From: Michal Svoboda <lvm@spatium.org>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] No device found for PV but is actually fine
Date: Fri, 9 May 2014 14:40:40 +0200 [thread overview]
Message-ID: <20140509124040.GA686@feynman.spatium.org> (raw)
In-Reply-To: <536CC710.4030708@redhat.com>
Marian Csontos wrote:
> Michal(-e), I suggest modifying global_filter to accept only the
> devices you want in the VG.
Hi,
I've tried playing with filter and global_filter in lvm.conf, but it did
not help - as if the conf file was ignored. I tried blacklisting and
whitelisting. Does something need to be restarted/rebooted for these
settings to take effect?
I then did some more experiments and eventually solved the issue.
First I tried pvscan --cache /dev/md0, at which point md0 was "accepted"
as existing PV, and the "system" VG would show up in vgdisplay. I was
even able to resize one of the LVs. However, after running pvscan --cache
with no extra agruments, I would receive the duplicate PV errors as in
previous e-mail and the "system" VG would disappear from vgdisplay. :-o
Finally I solved the issue by changing initcpio hook from "mdadm_udev"
to "mdadm". This is arch-linux specific thing that changes stuff that is
exported to the initial ramdisk used for boot. User-wise, that change
would stop using udev auto-magic for assembling md arrays, but use
/etc/mdadm.conf directly instead. I don't know the implementation details.
After that I receive *no more errors* about either missing or duplicate
PV and all VGs/LVs are displayed by the respective display commands. So
for me issue is solved but if anyone wants to get to the bottom I am
open to do some more experiments.
Michal Svoboda
next prev parent reply other threads:[~2014-05-09 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 10:45 [linux-lvm] No device found for PV but is actually fine Michal Svoboda
2014-05-08 14:00 ` Jack Waterworth
2014-05-09 12:16 ` Marian Csontos
2014-05-09 12:40 ` Michal Svoboda [this message]
2014-05-09 14:13 ` Marian Csontos
2014-05-13 19:26 ` Michal Svoboda
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=20140509124040.GA686@feynman.spatium.org \
--to=lvm@spatium.org \
--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;
as well as URLs for NNTP newsgroup(s).