[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Resizing file-based images
Ah, Thanks for this. I've only been sticking to file-based images as this is the only method that I can get working relatively quickly from a clean install. OK check this out:- df -h Filesystem Size Used Avail Use% Mounted on /dev/hda3 9.2G 3.3G 5.5G 37% / tmpfs 502M 0 502M 0% /lib/init/rw udev 10M 44K 10M 1% /dev tmpfs 502M 0 502M 0% /dev/shm /dev/hda1 92M 31M 56M 36% /boot /dev/hda5 28G 18G 9.0G 66% /home /dev/hda6 72G 26G 42G 39% /vz # << Used for file-based domUs If I had /dev/hda6 as LVM, a) Do I have something like :disk = [ 'phy:/vz/alpha/bxvm.img,sda1,w', 'phy:/vz/alpha/bxvm.swap,sda2,w']? I've never been able to get the LVM'ed instances going :-/ Thanks alot for your time! On 03/06/07, Tim Post <tim.post@xxxxxxxxxxx> wrote: On Sun, 2007-06-03 at 02:34 +0000, john maclean wrote: > Used the principles from here http://jailtime.org/howto:filesystem to > resize some file-based domUs. Everything's Ok but I've rebooted to a > new kernel and notice that `ls -alh /path/to/images` still shows the > original sizes of the domUs. When you use a file backed BD (especially as a sparse file) it will always claim the original size unless of course it becomes bigger. This does not mean that its the size LS is reporting it to be. Try looking at the output of 'du -h' noticing the partition containing the file backed BD's then compare it with the output of ls. I really recommend using LVM over file backed block devices unless your in a position where you just can't use LVM. > > What gives? > You are user 1,798,782,947,153,827,301 to be confused by this. Reality has not changed, your computer has not developed a drug habit, this is not a dream. Best, --Tim -- John Maclean - 07739 171 531 MSc (DIC) _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |