From: Chris Murphy <lists@colorremedies.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] bogus WARNING: Device for PV not found or rejected by a filter.
Date: Wed, 31 Jan 2018 21:18:07 -0700 [thread overview]
Message-ID: <CAJCQCtTc=exYokfTp54+gqd=theoXrOf2fWwfaPSf7_eLz2mnQ@mail.gmail.com> (raw)
Fedora 27 Server:
4.14.16-300.fc27.x86_64
lvm2-2.02.175-1.fc27.x86_64
Every 10 or so minutes in the journal, I'm getting what appears to be
a bogus warning. I say bogus because the PV is present, and I can
mount an XFS formatted LV found on this PV without error.
Jan 31 20:20:04 f27s.localdomain lvm[736]: WARNING: Device for PV
2zzRyd-4PXm-STvP-p5MA-dTsv-fJai-rAIpBH not found or rejected by a
filter.
Jan 31 20:20:04 f27s.localdomain lvm[736]: Cannot change VG 4vg while
PVs are missing.
Jan 31 20:20:04 f27s.localdomain lvm[736]: Consider vgreduce --removemissing.
Jan 31 20:20:04 f27s.localdomain lvm[736]: Cannot process volume group 4vg
Jan 31 20:20:04 f27s.localdomain lvm[736]: Failed command for 4vg-4pool-tpool.
vgdisplay -vv 4vg
https://paste.fedoraproject.org/paste/0KWAjAPBSg-fHjlGIBSyzA/raw
pvscan -vv
https://paste.fedoraproject.org/paste/HvutIxxAhy-rXJEuupytCg/raw
pvsck & vgck
https://paste.fedoraproject.org/paste/pFhpJh4fMqXCpbREW8hWIQ/raw
lvmdiskscan
https://paste.fedoraproject.org/paste/EdiSc4oQMUzRHPhxCfWYHw/raw
vgreduce --removemissing -t -vvvv 4vg
https://paste.fedoraproject.org/paste/TOTWyLcx4RBEkx67oe11PQ/raw
journal.log
https://drive.google.com/open?id=0B_2Asp8DGjJ9OThvS2Q3X3pWT3c
Decoder ring:
/dev/sdb is the relevant HDD in a USB enclosure
/dev/sdb1 is the only partition on it, LUKS
/dev/mapper/sdb is the unlocked LUKS device, which is also the PV in
question, and the only PV in the VG named "4vg"
--
Chris Murphy
next reply other threads:[~2018-02-01 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 4:18 Chris Murphy [this message]
2018-02-01 18:37 [linux-lvm] bogus WARNING Device for PV not found or rejected by a filter Chris Murphy
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='CAJCQCtTc=exYokfTp54+gqd=theoXrOf2fWwfaPSf7_eLz2mnQ@mail.gmail.com' \
--to=lists@colorremedies.com \
--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).