linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Andrea Tomassetti <andrea.tomassetti-opensource@devo.com>,
	Kent Overstreet <kent.overstreet@gmail.com>,
	linux-bcache@vger.kernel.org
Subject: Re: [RFC] Live resize of backing device
Date: Fri, 3 Feb 2023 10:41:28 +0800	[thread overview]
Message-ID: <C491B45E-B608-4590-BB8A-D24957D4D983@suse.de> (raw)
In-Reply-To: <3b52d311-9ab5-5fcc-3bb3-cc844caa2eb@ewheeler.net>



> 2023年2月3日 04:48,Eric Wheeler <bcache@lists.ewheeler.net> 写道:
> 
> On Fri, 3 Feb 2023, Coly Li wrote:
>>> 2023年1月27日 20:44,Andrea Tomassetti <andrea.tomassetti-opensource@devo.com> 写道:
>>> From 83f490ec8e81c840bdaf69e66021d661751975f2 Mon Sep 17 00:00:00 2001
>>> From: Andrea Tomassetti <andrea.tomassetti-opensource@devo.com>
>>> Date: Thu, 8 Sep 2022 09:47:55 +0200
>>> Subject: [PATCH v2] bcache: Add support for live resize of backing devices
>>> 
>>> Signed-off-by: Andrea Tomassetti <andrea.tomassetti-opensource@devo.com>
>>> ---
>>> Hi Coly,
>>> this is the second version of the patch. As you correctly pointed out,
>>> I implemented roll-back functionalities in case of error.
>>> I'm testing this funcionality using QEMU/KVM vm via libvirt.
>>> Here the steps:
>>> 1. make-bcache --writeback -B /dev/vdb -C /dev/vdc
>>> 2. mkfs.xfs /dev/bcache0
>>> 3. mount /dev/bcache0 /mnt
>>> 3. dd if=/dev/random of=/mnt/random0 bs=1M count=1000
>>> 4. md5sum /mnt/random0 | tee /mnt/random0.md5
>>> 5. [HOST] virsh blockresize <vm-name> --path <disk-path> --size <new-size>
>>> 6. xfs_growfs /dev/bcache0
>>> 6. Repeat steps 3 and 4 with a different file name (e.g. random1.md5)
>>> 7. umount/reboot/remount and check that the md5 hashes are correct with
>>>       md5sum -c /mnt/random?.md5
>> 
>> [snipped]
>> 
>> Hi Andrea,
>> 
>> For the above step 5, could you provide a specific command line for me to reproduce?
>> 
>> I tried to resize the disk by virsh from 400G to 800G, the disk resize 
>> doesn’t happen online, I have to stop and restart the virtual machine 
>> and see the resized disk.
> 
> Coly, 
> 
> The `virsh blockresize` command only informs the vm that the size has 
> changed. You will need to resize the disk itself using `lvresize` or 
> whatever your VM's backing device is. If you're backing device for the 
> virtual machine is a file, then you could use `truncate -s <size> 
> /file/path` before issuing `virsh blockresize`.
> 
> Another possibility: are you using virtio-blk as shown in his example, or 
> a different virtual driver like virtio-scsi?
> 

Yes, it was virtio-scsi drive.


> If the VM doesn't detect it you might need to do this if its a 
> virtio-scsi disk on the inside:
> 
> for i in /sys/class/scsi_host/*/scan; do echo - - - > $i; done
> 
> If you're using virtio-blk (vda) then it should be immediate.  I don't 
> think IDE will work at all, and not sure about nvme.

Sure, now I switch to virtio-blk drive and I can see the backing device size extends immediately after blockresize command in virsh.

Thanks.

Coly Li


  reply	other threads:[~2023-02-03  2:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 10:05 [RFC] Live resize of backing device Andrea Tomassetti
2022-08-04 14:32 ` Coly Li
2022-08-05 19:38 ` Eric Wheeler
2022-09-06 13:22   ` Andrea Tomassetti
2022-09-08  8:32     ` Andrea Tomassetti
2022-09-19 11:42       ` Andrea Tomassetti
2022-09-19 12:16         ` Coly Li
2022-12-09  8:57           ` Andrea Tomassetti
2022-12-09  9:36             ` Coly Li
2022-12-30 10:40       ` Coly Li
2023-01-11 16:01         ` Andrea Tomassetti
2023-01-17 13:08           ` Error messages with kernel 6.1.[56] Pierre Juhen
2023-01-17 16:08             ` Coly Li
2023-01-17 16:18           ` [RFC] Live resize of backing device Coly Li
2023-01-25 10:07             ` Andrea Tomassetti
2023-01-25 17:59               ` Coly Li
2023-01-27 12:44                 ` Andrea Tomassetti
2023-01-27 22:40                   ` Eric Wheeler
2023-01-31 10:20                     ` Andrea Tomassetti
2023-02-02 17:18                   ` Coly Li
2023-02-02 20:48                     ` Eric Wheeler
2023-02-03  2:41                       ` Coly Li [this message]
2023-02-19  9:39                   ` Coly Li
2023-02-20  8:27                     ` mingzhe
2023-02-20 12:29                       ` Coly Li
2023-02-22  8:42                         ` Andrea Tomassetti
2023-02-27 22:08                       ` Eric Wheeler
2023-02-28  2:46                         ` mingzhe
2023-01-27  2:53               ` [RFC] Live resize of bcache " Eric Wheeler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C491B45E-B608-4590-BB8A-D24957D4D983@suse.de \
    --to=colyli@suse.de \
    --cc=andrea.tomassetti-opensource@devo.com \
    --cc=bcache@lists.ewheeler.net \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).