The way I've done it in the past is:
1. Make sure that xen domain is shut down that you are re-sizing
2. Run lvextend (you've already done this)
3. Run e2fsck -f [logical volume name] (i.e. /dev/domain0/lvname)
4. Run resize2fs [volume name] [new size in G of LV] (i.e. resize2fs
/dev/domain0/lvname 8G
5. Start up vm. New size should be reflected now.
HTH
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of John S
Little
Sent: Friday, March 10, 2006 12:30 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] RE: domU lvm and resizing40
Ben..
>
> Depends on what OS you are using. For RHEL4, you can use either
oops-I'm using SlES 9 sp3.
> resize2fs (requires you to first run e2fsck), or (better choice) you 
> can
I tried resize2fs but maybe I didn't do right. I ran it from dom0
against the lv /dev/xenlocal/xen0vm1 volume. Is that the correct way
for a vm?
> also run ext2online, which doesn't require running e2fsck, but rather
ext2online looks as though it should be a part of ext2resize but if SuSE
is using it I haven't been able to find it.
> resizes it online.
>
> Ben
>
FWIW if I open yast from the vm and look at the partition manager it
also shows the new size.
Thanks,
John
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users