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] Issue on resizing domU root partition

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Issue on resizing domU root partition
From: Edson Marquezani Filho <edsonmarquezani@xxxxxxxxx>
Date: Mon, 5 Oct 2009 10:31:30 -0300
Delivery-date: Mon, 05 Oct 2009 06:32:17 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=7zbsDx9JmTlsR5CWICvC5pxPM4UdYllfmM0hjEBQYtE=; b=t805bgScoj5QgEBAur0RWTgfGGqEBfRJAMAYP/uCce1SZsh/gpEMtmVBeShnlq6zSa pJnxIGoXW0R5+j6lX3s+k4uyYYqaGHPmB8Wz/biwiMkjXnF1rbcOao9RoRobaWXyNVSb ZhKowN6fFc8uZLtgg7vokvp6G2XaZtwsq7aV8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=E3bY1Eqh9XqxVmgxmzB3DKv00llPADIj62KWHvyhCFf6azK0niwily+cCWkVnCPNpy Xl6GkJEK1jKUJ3f3KJPzpFquWIYUhS+ppMf3YnOdkBocDCVwEQfjZCEZyzLIpXH0hbNM UKCTZ3UVvG3JbejvRQZS5S3J7AEfpEKHVwfGs=
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
Hello everybody,

I need to resize a domU root partition, running EXT3, but I'm facing
some issue with pygrub, I supose.

My domU root disk is on a LV device. Before resizing, it looks like this:

[root@master]# fdisk -lu /dev/vgVMs/lvDbserver

Disk /dev/vgVMs/lvDbserver: 7516 MB, 7516192768 bytes
255 heads, 63 sectors/track, 913 cylinders, total 14680064 sectors
Units = setores of 1 * 512 = 512 bytes

           Dispositivo Boot      Start         End      Blocks   Id  System
/dev/vgVMs/lvDbserver1             128     4016249     2008061   82
Linux swap / Solaris
/dev/vgVMs/lvDbserver2   *     4016256    14667344     5325544+  83  Linux

(Note that partitions start blocks are not default because of RAID
alignment requisites.)

Ok, from the dom0 (and with domU turned off, off course) I extend the
LV, delete the second partition and recreate it with the same starting
block but bigger than before, matching the new LV size. After this, it
will look like this:

[root@master Agent]# fdisk -lu /dev/vgVMs/lvDbserver

Disk /dev/vgVMs/lvDbserver: 16.1 GB, 16106127360 bytes
255 heads, 63 sectors/track, 1958 cylinders, total 31457280 sectors
Units = setores of 1 * 512 = 512 bytes

             Dispositivo Boot      Start         End      Blocks   Id  System
/dev/vgVMs/lvDbserver1             128     4016249     2008061   82
Linux swap / Solaris
/dev/vgVMs/lvDbserver2         4016256    31455269    13719507   83  Linux

Ok, still from domU, I resize the second partition with resize2fs
(adding devices with kpartx -a before, and after removing mappings
with kpartx -d). Resizing suceeds ok, but when I try to start the
domU, it fails with that following message:

Traceback (most recent call last):
  File "/usr/bin/pygrub", line 658, in ?
    fs = fsimage.open(file, get_fs_offset(file))
  File "/usr/bin/pygrub", line 117, in get_fs_offset
    offset += get_solaris_slice(file, offset)
  File "/usr/bin/pygrub", line 80, in get_solaris_slice
    raise RuntimeError, "Invalid disklabel magic"
RuntimeError: Invalid disklabel magic
No handlers could be found for logger "xend"
Error: Boot loader didn't return any data!

(I know that filesystem has not been corrupted, because I can even
mount it sucesfull on dom0, if I try.)

What could be wrong? Would be that a pygrub bug, or am I missing something?

I'm using Red Hat Enterprise here, with Xen hypervisor 3.1.2, and kernel 2.6.18.

I would be very thankful if anybody could help me. Thank you.

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>