Hello, I am using Xen 4.0.1 and Xen 3.2.1 dom0 with Debian Lenny and Squeeze dom0s. I have a bunch of virtual machines running , all using LVM as backend storage. Mostly, an LVM logical volume is mapped to a partition in the VM (eg: xvda1) I have tried to hot resize the filesystem in the VM without umounting it but it just do not work... Here is what I did: - lvextend on the dom0, - resize2fs on the VM Doing so, the kernel of the virtual machine seems not to see the space available for the partition has changed and resize2fs returns: "xvda already has xxxxxxxxx blocks, Nothing to do" This last until I hot remove the disk from the VM using xm block-detach and re-attach it using xm block attach. After re-attaching the disk I can resize2fs as expected. Is there anything I can do to avoid detaching the block device from the VM to let the kernel know the partition has a new size? What are the bests practices in Xen to achieve hot resize of filesystem in the VM? Regards. -- <http://www.horoa.net> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Aug 11, 2011 at 4:40 PM, Alexandre Chapellon <a.chapellon@horoa.net> wrote:> > Hello, > > I am using Xen 4.0.1 and Xen 3.2.1 dom0 with Debian Lenny and Squeeze dom0s. > I have a bunch of virtual machines running , all using LVM as backend storage. > Mostly, an LVM logical volume is mapped to a partition in the VM (eg: xvda1) > I have tried to hot resize the filesystem in the VM without umounting it but it just do not work... Here is what I did: > > - lvextend on the dom0, > - resize2fs on the VM > > Doing so, the kernel of the virtual machine seems not to see the space available for the partition has changed and resize2fs returns: "xvda already has xxxxxxxxx blocks, Nothing to do" > > This last until I hot remove the disk from the VM using xm block-detach and re-attach it using xm block attach. > After re-attaching the disk I can resize2fs as expected. >That is expected behaviour.> > Is there anything I can do to avoid detaching the block device from the VM to let the kernel know the partition has a new size? > What are the bests practices in Xen to achieve hot resize of filesystem in the VM?Newer version of xen and domU kernel allows domU to detect block device change without having to detach/reboot. Try using domU kernel form Jeremy''s git tree. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Le 11/08/2011 11:53, Fajar A. Nugraha a écrit :> On Thu, Aug 11, 2011 at 4:40 PM, Alexandre Chapellon > <a.chapellon@horoa.net> wrote: >> Hello, >> >> I am using Xen 4.0.1 and Xen 3.2.1 dom0 with Debian Lenny and Squeeze dom0s. >> I have a bunch of virtual machines running , all using LVM as backend storage. >> Mostly, an LVM logical volume is mapped to a partition in the VM (eg: xvda1) >> I have tried to hot resize the filesystem in the VM without umounting it but it just do not work... Here is what I did: >> >> - lvextend on the dom0, >> - resize2fs on the VM >> >> Doing so, the kernel of the virtual machine seems not to see the space available for the partition has changed and resize2fs returns: "xvda already has xxxxxxxxx blocks, Nothing to do" >> >> This last until I hot remove the disk from the VM using xm block-detach and re-attach it using xm block attach. >> After re-attaching the disk I can resize2fs as expected. >> > That is expected behaviour. > >> Is there anything I can do to avoid detaching the block device from the VM to let the kernel know the partition has a new size? >> What are the bests practices in Xen to achieve hot resize of filesystem in the VM? > Newer version of xen and domU kernel allows domU to detect block > device change without having to detach/reboot. Try using domU kernel > form Jeremy''s git tree.I got it working using a debian xen kernel instead of the default xen kernel. In which kernel version did this feature appeared in mainstream? -- <http://www.horoa.net> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users