You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the weblog Xen: how do i alert a domU to an lvresize on dom0?

#2 Re: Xen: how do i alert a domU to an lvresize on dom0? Posted by dkg (216.254.xx.xx) on Tue 19 Jun 2007 at 23:21 Well, i didn't say i had a filesystem on the block device, actually. Say the block device is present on the domU, but currently unused. I'd want to create a filesystem on the block device from the domU, but i would want it to know the real value of the block device, which it currently doesn't know, according to domU:/proc/partitions. I shouldn't have to reboot the domU for that, should I? Besides, if it is already a filesystem (and currently mounted in the domU, and the filesystem is ext3, and the domU is running a modern kernel), resize2fs can grow filesystems while mounted these days, as long as it can see the larger underlying block device. So i guess this doesn't quite give me the answer i'm looking for yet. If a Xen guest needs to be rebooted to see a change in size of a block device, that's one thing. But i don't think resize2fs on its own is a reason to have to reboot.

Username:	Anonymous
Title:
Your Comment:
Posting Format:	BBCode HTML Text Plain Text Textile

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account