Re: [Xen-devel][PATCH]: Support dynamic resizing of vbds

["Ky Srinivasan" <ksrinivasan@xxxxxxxxxx>]

>>> On 7/20/2010 at  2:27 PM, in message <20100720182733.GQ17817@xxxxxxxxxxx>, 
>>> Pasi
KÃrkkÃinen<pasik@xxxxxx> wrote: 
> On Mon, Mar 15, 2010 at 09:05:09PM -0600, Ky Srinivasan wrote:
>> >> >
>> >> 
>> >> I tested the patch on xen-sources-2.6.31-r12 and it appears to work 
>> >> perfectly:
>> >> 
>> >> dom0: VBD Resize: new size 172032
>> >> domU: Setting capacity to 172032
>> >>
>> > 
>> > Btw it would be good to add the vbd-device and domU name to these log 
> entries 
>> > in the dom0,
>> > and the device name in domU!
>> 
>> Agreed. Will send out the patch soon.
>> 
> 
> Hey,
> 
> Did you send this patch? I'm just wondering if I missed it..
> 
> -- Pasi
If I recall correctly I think I sent the patches out.

K. Y
> 
>> >  
>> >> I extended the filesystem and filled up the available space, then
>> >> extended again:
>> >> 
>> >> dom0: VBD Resize: new size 376832
>> >> domU: Setting capacity to 376832
>> >> 
>> >> fsck, badblocks, and testing a tarball I had filled the filesystem
>> >> with revealed no problems, so I decided to try reducing the
>> >> filesystem, first using resize2fs, then reducing the size of the block
>> >> device, although some errors were logged in domU the operation seemed
>> >> to work ok:
>> >> 
>> >> dom0: VBD Resize: new size 114688
>> >> domU: Setting capacity to 114688
>> >> domU: end_request: I/O error, dev sdb1, sector 212984
>> >> domU: Buffer I/O error on device sdb1, logical block 26623
>> >> 
>> >> I did notice that it seemed to be necessary to "poke" the device using
>> >> cfdisk /dev/sdb1 before domU would notice the new size, but on the
>> >> whole everything works nicely and this is a very useful new feature!
>> >> 
>> > 
>> > Good to hear it works!
>> > 
>> > -- Pasi
>> 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel