From: Zdenek Kabelac <firstname.lastname@example.org>
To: LVM2 development <email@example.com>,
Eric Ren <firstname.lastname@example.org>
Cc: LVM general discussion and development <email@example.com>
Subject: Re: [linux-lvm] Aborting. LV mythinpool_tmeta is now incomplete
Date: Fri, 12 Apr 2019 15:44:18 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Dne 12. 04. 19 v 12:42 Eric Ren napsal(a):
>> 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?
There is very low number of lvm developer and very high number of generated
different error states from udev ;)
So far we have not though about this one - so we will need to think whether
we can figure out something for these sorts of errors...
IMHO it looks like /dev/__ symlink in your case occasionally points to
different device - and this is confusing lvm2
(and resent version even more as they is way more open/close sequences beyond
the point I'd like to see...)
>> 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!
Filters can fix a loooot of trouble we are otherwise having hard times to
figure out the right sequence....
So whenever you can - set your filter as tight as possible - this will speedup
execution of any lvm2 command and reduce risk of accessing unwanted devices...
prev parent reply other threads:[~2019-04-12 13:44 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
2019-04-12 13:44 ` Zdenek Kabelac [this message]
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).