I''m trying to add vbd resize to GPLPV, but it doesn''t seem to work: xm block-attach w2k3test32 phy:/dev/vg-xen/virt-test-0 hdb w xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576 lvextend --size=+1M /dev/vg-xen/virt-test-0 xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576 The xenstore backend isn''t updated to reflect the new size of the device... a strings | grep size of xen-blkback.ko module says: <6>xen-blkback:VBD Resize: Domid: %d, Device: (%d, %d) <6>xen-blkback:VBD Resize: new size %llu <4>xen-blkback:Error writing new size So the code is definitely there, it''s just not noticing that the device has been resize. Any suggestions? Thanks James
> > I''m trying to add vbd resize to GPLPV, but it doesn''t seem to work: > > xm block-attach w2k3test32 phy:/dev/vg-xen/virt-test-0 hdb w > > xenstore-read /local/domain/0/backend/vbd/377/832/sectors > =44056576 > > lvextend --size=+1M /dev/vg-xen/virt-test-0 > > xenstore-read /local/domain/0/backend/vbd/377/832/sectors > =44056576 > > The xenstore backend isn''t updated to reflect the new size of the device... a > strings | grep size of xen-blkback.ko module says: > <6>xen-blkback:VBD Resize: Domid: %d, Device: (%d, %d) > <6>xen-blkback:VBD Resize: new size %llu > <4>xen-blkback:Error writing new size > > So the code is definitely there, it''s just not noticing that the device has been > resize. > > Any suggestions? >My bad. I just checked the code and there actually has to be ring activity for the resize to be detected. James