From: Lupe Christoph <lupe@lupe-christoph.de>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Allocation maps of a mirrored LV?
Date: Thu, 15 Jan 2009 09:36:56 +0100 [thread overview]
Message-ID: <20090115083656.GL21131@lupe-christoph.de> (raw)
In-Reply-To: <b072968d0901141258n12aaea7nbccf0700bdda4512@mail.gmail.com>
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@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 |
next prev parent reply other threads:[~2009-01-15 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 10:09 [linux-lvm] Allocation maps of a mirrored LV? Lupe Christoph
2009-01-14 20:58 ` David Robinson
2009-01-15 8:36 ` Lupe Christoph [this message]
2009-01-15 9:30 ` Jaroslav Stava
2009-01-15 10:03 ` Lupe Christoph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090115083656.GL21131@lupe-christoph.de \
--to=lupe@lupe-christoph.de \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox