From: "Bryn M. Reeves" <bmr@redhat.com>
To: Bryan Kadzban <bryan@kadzban.is-a-geek.net>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Found duplicate PVs
Date: Tue, 12 Aug 2008 14:40:07 +0100 [thread overview]
Message-ID: <48A192B7.7000108@redhat.com> (raw)
In-Reply-To: <48A186A7.3050901@kadzban.is-a-geek.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bryan Kadzban wrote:
> Bryn M. Reeves wrote:
>>> broken (split) RAID1 mirror?
>
> Alternately, software RAID1 -- either a dm-raid type setup (most onboard
> "RAID controllers", and in fact almost every consumer "RAID" device) or
> md?
That's exactly what I meant by a split/broken RAID1 mirror - either two
disks being presented as SCSI/ATA devices when they contain an array or
an array "controller" (fakeraid) using the wrong drivers. Unlikely to be
MD since LVM2 already performs MD component detection (enabled by
default iirc) and will use the MD device in preference to components.
> You can control which devices get scanned by editing the "filter" option
> in /etc/lvm/lvm.conf -- you can make it only include the RAID array
> device (/dev/mapper/whatever or /dev/mdX), instead of the member drives
> (/dev/sdXY).
Shouldn't be needed for MD devices - just make sure you have:
devices {
[...]
md_component_detection = 1
}
Somewhere in your lvm.conf. As you say, this is most common with dmraid
since the "controller" is just a regular ATA part with some BIOS goop
and a bit of metadata on the disks but you can get the same sort of
behavior with "real" RAID controllers in some cases.
> (And this is probably just a special case of the "broken (split) RAID1
> mirror" possibility that Bryn was talking about.)
Yup :)
Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFIoZK36YSQoMYUY94RAid3AKDFmEtVBuIBCKOhNJbsC70oVcRdzgCdFRQs
BjW8XPFFatq0y8GpER6GI+c=
=vplQ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-08-12 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 11:24 [linux-lvm] Found duplicate PV 7TGP3THphAvROCTtC4OI2gZrvrAGrn15: using /dev/sdah not /dev/sdq Found duplicate PV Qbpd3ov1sd3GHCwCQHUzkI00X53lbcDC: using /dev/sdai not /dev/sdr Found duplicate PV v0YURmuRm51dfY8br0Bx7XxOOIJyV6oa: using /dev/sdt not /dev/sdc Found Pedro Gonzalez Zamora
2008-08-12 11:31 ` Bryn M. Reeves
2008-08-12 12:48 ` [linux-lvm] Found duplicate PVs Bryan Kadzban
2008-08-12 13:40 ` Bryn M. Reeves [this message]
2008-08-12 14:10 ` Pedro Gonzalez Zamora
2008-08-12 15:27 ` Bryan Kadzban
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=48A192B7.7000108@redhat.com \
--to=bmr@redhat.com \
--cc=bryan@kadzban.is-a-geek.net \
--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