Re: [Xen-users] LV resize encrypted volume

[Jan Bakuwel <jan.bakuwel@xxxxxxxxx>]

Hi Fajar,

...snap...

> Here's something that would help you understand better. In domU, do a
> "cat /proc/partitions" and "fdisk -lu".
> You should see that domU sees the "disk" HAS changed, but the
> partition ON that disk remains the same

Not really.

Here's the relevant part of the output from "cat /proc/partitions":

domU:~# cat /proc/partitions
major minor  #blocks  name

   8    81  524288000 sdc1
254     0  524287484 dm-0

As you can see domU thinks sdc1 is 524288000 units.

Then the relevant part of the output of "fdisk -lu" shows:

domU:~# fdisk -lu
...snap...
Disk /dev/sdc1: 536.8 GB, 536870912000 bytes
255 heads, 63 sectors/track, 65270 cylinders, total 1048576000 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x08020000

Disk /dev/sdc1 doesn't contain a valid partition table
...snap...


And "blockdev --getsz /dev/sdc1 shows:

domU:~# blockdev --getsz /dev/sdc1
1048576000


I'm not using an installer to create my VMs but mount the LV on dom0,
then unpack the tarball of my choice, unmount the LV on dom0 and start
domU. I've been doing that for years; works like a charm.


Now on dom0:

dom0:~# blockdev --getsz /dev/d/lv3
1258291200

dom0:~# cat /proc/partitions
...snap...
 254     3  629145600 dm-3
...snap...

1258291200 / 2 (512 byte sectors) = 629145600 (1K blocks)

cheers,
Jan


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users