diff options
| author | Vivek Goyal <vgoyal@redhat.com> | 2012-03-29 10:09:44 +0200 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2012-03-29 10:09:44 +0200 |
| commit | e9986f303dc0f285401de28cf96f42f4dd23a4a1 (patch) | |
| tree | 2b13f119efc6984c70b7e3570c8cffde0c1f53c7 /drivers/block | |
| parent | 6674fb79ca9c19f5ee3d4cd683da2d9e09cfc9b8 (diff) | |
| download | op-kernel-dev-e9986f303dc0f285401de28cf96f42f4dd23a4a1.zip op-kernel-dev-e9986f303dc0f285401de28cf96f42f4dd23a4a1.tar.gz | |
virtio-blk: Call revalidate_disk() upon online disk resize
If a virtio disk is open in guest and a disk resize operation is done,
(virsh blockresize), new size is not visible to tools like "fdisk -l".
This seems to be happening as we update only part->nr_sects and not
bdev->bd_inode size.
Call revalidate_disk() which should take care of it. I tested growing disk
size of already open disk and it works for me.
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/block')
| -rw-r--r-- | drivers/block/virtio_blk.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c index c4a60ba..0e4ef3d 100644 --- a/drivers/block/virtio_blk.c +++ b/drivers/block/virtio_blk.c @@ -351,6 +351,7 @@ static void virtblk_config_changed_work(struct work_struct *work) cap_str_10, cap_str_2); set_capacity(vblk->disk, capacity); + revalidate_disk(vblk->disk); done: mutex_unlock(&vblk->config_lock); } |
