[linux-lvm] Allocation maps of a mirrored LV?

[Lupe Christoph]

On Wednesday, 2009-01-14 at 20:58:28 +0000, David Robinson wrote:
> On Tue, Jan 13, 2009 at 10:09 AM, Lupe Christoph <lupe at lupe-christoph.de> wrote:

> > I'm about to integrate support for LVM mirrors into the configuration
> > management system I'm maintaining for a client. This system has a "scan"
> > function that retrieves the current configuration and compares it
> > against a database.

> > My problem is that I'm unable to get the allocation info for the parts
> > of a mirrored volume under SLES 10 (lvm2 RPM is at 2.02.17, even
> > OpenSuSE 10.3 has only lvm2 2.02.25).

> > lvdisplay --maps only gives me:

> Try pvs/vgs/lvs instead (and use -o to get the details you want):

> # pvs --segments
>   PV         VG     Fmt  Attr PSize  PFree  Start SSize
>   /dev/dm-0  laptop lvm2 a-   55.69G 32.00M     0   250
>   /dev/dm-0  laptop lvm2 a-   55.69G 32.00M   250  1499
>   /dev/dm-0  laptop lvm2 a-   55.69G 32.00M  1749    32
>   /dev/dm-0  laptop lvm2 a-   55.69G 32.00M  1781     1

OK, let me show you. I created an LV with:
lvcreate --name testlv0 --size 100m --mirror 1 testvg

lvs -o +devices
  LV              VG     Attr   LSize   Origin Snap%  Move Log          Copy%  Devices
  testlv0         testvg mwi-a- 100.00M                    testlv0_mlog 100.00 testlv0_mimage_0(0),testlv0_mimage_1(0)

Any other suggestion for a -o option? I tried stripes, segtype, seg_start,
seg_size, seg_tags, regionsize, mirror_log and lvs --segments.

I can't find an option for pvs that prints the allocation map, nor for
vgs. Any suggestions?

Lupe Christoph
-- 
| There is no substitute for bad design except worse design.                   |
| /me                                                                          |