From: Eric Ren <email@example.com>
To: Zdenek Kabelac <firstname.lastname@example.org>
Cc: LVM general discussion and development <email@example.com>,
LVM2 development <firstname.lastname@example.org>
Subject: Re: [linux-lvm] [lvm-devel] Aborting. LV mythinpool_tmeta is now incomplete
Date: Fri, 12 Apr 2019 18:42:40 +0800 [thread overview]
Message-ID: <CAKM4AexgHS64pm8CE4PhToUCL_12j0KzAPV-XJ5HNGxvVn5rSA@mail.gmail.com> (raw)
> Looking at provided log file - the system seems to be using some weird udev
> rule - which results in generating strange /dev/__ symlinks.
Yes! I also see these weird device names, but I don't have a good
explanation for it, so that I'm stupid to think deep into it.
> There are already visible some other devices like i.e.:
> /dev/disk/by-id/virtio-instance-store0___O-part1 pointing to /dev/vda1
So, the broken device path/symbol is only related to udev, lvm just
get the device list from udev DB right?
Do you think such issue can make LVM think the disk is missing?
> BTW - you can always setup filter (and you really SHOULD in this case),
> to whitelist devices for scanning to avoid similar issues.
> I assume you want to set something like a|/dev/vd|, r|.*|
> Also you should collect udev rules and post them here so we can check
> which rule could be suspected.
Thanks! From this, I've learned how import device filter setup is!
- Eric Ren
next prev parent reply other threads:[~2019-04-12 10:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 0:27 [linux-lvm] Aborting. LV mythinpool_tmeta is now incomplete Eric Ren
2019-04-11 10:01 ` Eric Ren
2019-04-11 11:21 ` [linux-lvm] [lvm-devel] " Zdenek Kabelac
2019-04-11 11:03 ` [linux-lvm] " Zdenek Kabelac
2019-04-11 11:26 ` Eric Ren
2019-04-11 11:32 ` Zdenek Kabelac
2019-04-11 11:49 ` Eric Ren
2019-04-11 12:12 ` Zdenek Kabelac
2019-04-11 13:09 ` Eric Ren
2019-04-11 13:13 ` Zdenek Kabelac
[not found] ` <CAKM4Aez9H=GuRLK0EDJTwpb7j34tCu1aY4dS5_L4saDGERestg@mail.gmail.com>
2019-04-11 17:33 ` Eric Ren
2019-04-12 10:05 ` [linux-lvm] [lvm-devel] " Zdenek Kabelac
2019-04-12 10:42 ` Eric Ren [this message]
2019-04-12 13:44 ` [linux-lvm] " Zdenek Kabelac
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).