This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] unexpected sizes

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] unexpected sizes
From: Brian Krusic <brian@xxxxxxxxxx>
Date: Thu, 15 Jan 2009 15:24:18 -0800
Delivery-date: Wed, 04 Feb 2009 09:38:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

So I shutdown my domU to copy it to a backup location (yes, I am still trying to find a way to do a live backup/snapshot so if anyone has suggestions, I would love to hear).

So, du -h /var/lib/xen/images/host.img

... shows 18G

So I copy it to my NFS mounted backup machine and upon doing a du -h / nfs-share/backups/host.img

... show 7.6G.

This domU is actually set to have 300G but I didn't allocate all of the disk space during domU creation.

Any ideas?  I would prefer some predictability here.

Incidentally, from within the domU itself, I do a df -h and I get;

/dev/mapper/VolGroup00-LogVol00 282G size, 5.2G used, 263G available
/dev/xvda1 99M size, 21M used, 74M available
tmpfs 2.0G size, 0 used, 2.0G available

- Brian

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] unexpected sizes, Brian Krusic <=