From: Zdenek Kabelac <zkabelac@redhat.com> To: LVM2 development <lvm-devel@redhat.com>, Eric Ren <renzhengeek@gmail.com> Cc: LVM general discussion and development <linux-lvm@redhat.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: <e1c1f1c2-2717-25cd-e063-50df9df04c4f@redhat.com> (raw) In-Reply-To: <CAKM4AexgHS64pm8CE4PhToUCL_12j0KzAPV-XJ5HNGxvVn5rSA@mail.gmail.com> Dne 12. 04. 19 v 12:42 Eric Ren napsal(a): > Hi! > >> 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. > Thanks!!! > >> 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? Hi 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... Regards Zdenek
WARNING: multiple messages have this Message-ID (diff)
From: Zdenek Kabelac <zkabelac@redhat.com> To: lvm-devel@redhat.com Subject: Aborting. LV mythinpool_tmeta is now incomplete Date: Fri, 12 Apr 2019 15:44:18 +0200 [thread overview] Message-ID: <e1c1f1c2-2717-25cd-e063-50df9df04c4f@redhat.com> (raw) In-Reply-To: <CAKM4AexgHS64pm8CE4PhToUCL_12j0KzAPV-XJ5HNGxvVn5rSA@mail.gmail.com> Dne 12. 04. 19 v 12:42 Eric Ren napsal(a): > Hi! > >> 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. > Thanks!!! > >> 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? Hi 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... Regards Zdenek
next prev parent reply other threads:[~2019-04-12 13:44 UTC|newest] Thread overview: 28+ 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 0:27 ` Eric Ren 2019-04-11 10:01 ` [linux-lvm] " Eric Ren 2019-04-11 10:01 ` Eric Ren 2019-04-11 11:21 ` [linux-lvm] [lvm-devel] " Zdenek Kabelac 2019-04-11 11:21 ` Zdenek Kabelac 2019-04-11 11:03 ` [linux-lvm] " Zdenek Kabelac 2019-04-11 11:03 ` Zdenek Kabelac 2019-04-11 11:26 ` [linux-lvm] " Eric Ren 2019-04-11 11:26 ` Eric Ren 2019-04-11 11:32 ` [linux-lvm] " Zdenek Kabelac 2019-04-11 11:32 ` Zdenek Kabelac 2019-04-11 11:49 ` [linux-lvm] " Eric Ren 2019-04-11 11:49 ` Eric Ren 2019-04-11 12:12 ` [linux-lvm] " Zdenek Kabelac 2019-04-11 12:12 ` Zdenek Kabelac 2019-04-11 13:09 ` [linux-lvm] " Eric Ren 2019-04-11 13:09 ` Eric Ren 2019-04-11 13:13 ` [linux-lvm] " Zdenek Kabelac 2019-04-11 13:13 ` Zdenek Kabelac [not found] ` <CAKM4Aez9H=GuRLK0EDJTwpb7j34tCu1aY4dS5_L4saDGERestg@mail.gmail.com> 2019-04-11 17:33 ` [linux-lvm] " Eric Ren 2019-04-11 17:33 ` Eric Ren 2019-04-12 10:05 ` [linux-lvm] [lvm-devel] " Zdenek Kabelac 2019-04-12 10:05 ` Zdenek Kabelac 2019-04-12 10:42 ` [linux-lvm] [lvm-devel] " Eric Ren 2019-04-12 10:42 ` Eric Ren 2019-04-12 13:44 ` Zdenek Kabelac [this message] 2019-04-12 13:44 ` Zdenek Kabelac
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=e1c1f1c2-2717-25cd-e063-50df9df04c4f@redhat.com \ --to=zkabelac@redhat.com \ --cc=linux-lvm@redhat.com \ --cc=lvm-devel@redhat.com \ --cc=renzhengeek@gmail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.