Re: [Qemu-devel] [Qemu-block] [Nbd] How to online resize qemu disk with nbd protocol?
> On 12 Jan 2017, at 18:45, Eric Blakewrote: > > On 01/12/2017 11:57 AM, Bob Chen wrote: >> There might be a time window between the NBD server's resize and the >> client's `re-read size` request. Is it safe? > > For resize larger, it seems that it would be safe for the server to just > remember the last size it has advertised to the client. As long as the > client doesn't request read/write to any offset beyond the > last-advertised size (either the size the server gave at handshake, or > the size that the server reported when the client last used the new > 're-read size' command), there's no difference in behavior (and > well-behaved clients fall in this group); if the client DOES try to > access out-of-bounds with respect to the last known size, the server > SHOULD reject the access, but MAY serve it instead. A client that is > unaware of the 're-read size' command will never learn that the server > is now offering a larger image. > > For resize smaller, things are a lot trickier - how do you block access > to a portion of a file that the client still thinks exist, but which the > server has truncated away? Maybe the easy way out is to state that the > server MUST NOT resize smaller. I'm not sure why this is any harder than Qemu writing to a physical partition that changes size. You need to change the size of things in order. To resize smaller, you tell Qemu it's smaller, then resize the partition. To resize larger, you resize the partition then tell Qemu it's larger. This is incidentally exactly the same thing you do if you have a filing system on a partition (or a filing system on a real nbd device - we could support the same reread of geometry in kernel). >> >> What about an active `resize` request from the client? Considering some NBD >> servers might have the capability to do instant resizing, not applying to >> LVM or host block device, of course... > > And perhaps the 're-read size' command can serve a dual purpose. Since > all NBD commands already include space for size and offset parameters, > we could define that if the client passes 0/0 for size and offset, it > wants to read the server's current size; if it passes 0/non-zero, it is > asking the server to resize to the new non-zero size (and the server's > success or error response tells whether the resize happened). > > Should I spend time turning this idea into a more formal spec, along the > lines of other NBD extension proposals? I'd support the reread bit. I'm less sure we ever want to push a new size from the client. It seems a bit like a layering violation. Perhaps I can be convinced. My preferred way to do this would be essentially to allow NBD_OPT_INFO to be sent (wrapped appropriately) during the main transmission phase. That would allow *any* INFO stuff to be reread. If it's just this (rather than a resize command) I guess it could go into the NBD_OPT_INFO extension branch. If it's going to do more than _INFO_, then I guess it needs its own extension. -- Alex Bligh signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Qemu-devel] [Qemu-block] [Nbd] How to online resize qemu disk with nbd protocol?
On 01/12/2017 11:57 AM, Bob Chen wrote: > There might be a time window between the NBD server's resize and the > client's `re-read size` request. Is it safe? For resize larger, it seems that it would be safe for the server to just remember the last size it has advertised to the client. As long as the client doesn't request read/write to any offset beyond the last-advertised size (either the size the server gave at handshake, or the size that the server reported when the client last used the new 're-read size' command), there's no difference in behavior (and well-behaved clients fall in this group); if the client DOES try to access out-of-bounds with respect to the last known size, the server SHOULD reject the access, but MAY serve it instead. A client that is unaware of the 're-read size' command will never learn that the server is now offering a larger image. For resize smaller, things are a lot trickier - how do you block access to a portion of a file that the client still thinks exist, but which the server has truncated away? Maybe the easy way out is to state that the server MUST NOT resize smaller. > > What about an active `resize` request from the client? Considering some NBD > servers might have the capability to do instant resizing, not applying to > LVM or host block device, of course... And perhaps the 're-read size' command can serve a dual purpose. Since all NBD commands already include space for size and offset parameters, we could define that if the client passes 0/0 for size and offset, it wants to read the server's current size; if it passes 0/non-zero, it is asking the server to resize to the new non-zero size (and the server's success or error response tells whether the resize happened). Should I spend time turning this idea into a more formal spec, along the lines of other NBD extension proposals? -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: [Qemu-devel] [Qemu-block] [Nbd] How to online resize qemu disk with nbd protocol?
There might be a time window between the NBD server's resize and the client's `re-read size` request. Is it safe? What about an active `resize` request from the client? Considering some NBD servers might have the capability to do instant resizing, not applying to LVM or host block device, of course... Regards, Bob 2017-01-13 0:54 GMT+08:00 Stefan Hajnoczi: > On Thu, Jan 12, 2017 at 3:44 PM, Alex Bligh wrote: > >> On 12 Jan 2017, at 14:43, Eric Blake wrote: > >> That's because the NBD protocol lacks a resize command. You'd have to > >> first get that proposed as an NBD extension before qemu could support > it. > > > > Actually the NBD protocol lacks a 'make a disk with size X' command, > > let alone a resize command. The size of an NBD disk is (currently) > > entirely in the hands of the server. What I think we'd really need > > would be a 'reread size' command, and have the server capable of > > supporting resizing. That would then work for readonly images too. > > That would be fine for QEMU. Resizing LVM volumes or host block > devices works exactly like this. > > Stefan > >
Re: [Qemu-devel] [Qemu-block] [Nbd] How to online resize qemu disk with nbd protocol?
On Thu, Jan 12, 2017 at 3:44 PM, Alex Blighwrote: >> On 12 Jan 2017, at 14:43, Eric Blake wrote: >> That's because the NBD protocol lacks a resize command. You'd have to >> first get that proposed as an NBD extension before qemu could support it. > > Actually the NBD protocol lacks a 'make a disk with size X' command, > let alone a resize command. The size of an NBD disk is (currently) > entirely in the hands of the server. What I think we'd really need > would be a 'reread size' command, and have the server capable of > supporting resizing. That would then work for readonly images too. That would be fine for QEMU. Resizing LVM volumes or host block devices works exactly like this. Stefan