On Saturday 11 March 2006 3:26 pm, Christopher G. Stach II wrote:
> Fraser Campbell wrote:
> > Definitely do not resize the filesystem from dom0 while the domU is
> > running, I expect that may give the appearance of working but it will
> > likely corrupt your filesystem.
>
> Every time I've resized an LV inside of the dom0, the domU doesn't pick
> up the new size until a reboot. Then resize2fs works just fine. I've
> never had any corruption with resizing an LV with a domU running.
Fraser advice it correct, do not resize the *filesistem* from dom0 while domU
is running. resizing the *volume* is ok. it's important to differentiate
the two resizing steps.
i think John's original problem was that he did lvresize to resize the volume,
but didn't resize the filesystem. later he used resize2fs, but SuSE systems
use mostly reiser, so he should've used resize_reiserfs.
the first step (volume resizing, with lvresize) is usually done from dom0
(since domU usually sees a single volume, not the LVM); no harm doing it
while domU is running, but it might have to be restarted to pick up the new
volume size. (there should be a xend command to make it reread the new size
and propagate it to the domU)
the second step (filesystem resizing, with resize2fs, resize_reiserfs, etc)
can either be done from the running domU (if the filesystem supports online
resizing), or from dom0, with domU stopped (even with the most online-capable
filesystem!!)
--
Javier
pgpf5LvobQzdg.pgp
Description: PGP signature
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home