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] Resizing DomUs

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Resizing DomUs
From: "Harold A. Giménez Ch." <harold.gimenez@xxxxxxxxx>
Date: Mon, 3 Nov 2008 22:50:06 -0500
Delivery-date: Mon, 03 Nov 2008 19:50:51 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=VtTRlmS540b85AZswVU2UKc9Em9cW4PHDUvtXnlhvrE=; b=RBGkzRJkSNqKQh43jF14GMXAgBJ1U4rTOEvinhy7cWi0E7ZoWzmjb5pHKkSSX8hgv8 s6hs86oitn8AF8W4jH5A33260flqJXliDQPdzW5YFtPrgWdg+1YXbYdlp+qn7fkx3SgZ D/LngFrIi9fBE58SrA8SqdN4UBH30fnh7CZs0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=jEi3bHc+TEMzZxo/NoX5/tFwFpDbgTbJi5QuL6/YGxub/zinliLFb9uC3kIcVIRjYf 2mnwV4SrgXSgBg3g9b1j3zIbbpD37Ee4HwYwdcm5cpePKECqnNLoBfitaUTKA2A4DiKF L/eoohea2NqEeaxVop0nXXBcwpmFhKMc6zAKs=
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 group,

I'm sure this has been discussed numerous times, but I would like some pointers on troubleshooting the resizing of a DomU built on an image file (not LVM).

To add another 20GB, I tried running the following, as root:

dd if=/dev/zero bs=1M count=20480 >> img_file.img
20480+0 records in
20480+0 records out
21474836480 bytes (21 GB) copied, 1578.68 s, 13.6 MB/s
/sbin/resize2fs img_file.img
resize2fs 1.40.4 (31-Dec-2007)
/sbin/resize2fs: Bad magic number in super-block while trying to open img_file.img
Couldn't find valid filesystem superblock.

Also, this command fails:
/sbin/e2fsck -f img_file.img

I have several DomUs running and are very stable. However, the e2fsck fails on all of them. What am I doing wrong?

Thanks for any help you can provide,

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>