From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <47346a29-e6c7-6e22-4360-2d07e2ec7be3@redhat.com> <7839ff52-18e5-6a95-9a2a-12ea73457700@redhat.com> <62151b2e-c21a-177e-f66b-e2e08857be17@redhat.com> <6514b2be-67d7-3dfe-38b9-95e3bb39f55a@redhat.com> <7b17539c-749c-154f-d777-1d80d562a7f6@redhat.com> In-Reply-To: <7b17539c-749c-154f-d777-1d80d562a7f6@redhat.com> From: Eric Ren Date: Fri, 12 Apr 2019 18:42:40 +0800 Message-ID: Subject: Re: [linux-lvm] [lvm-devel] Aborting. LV mythinpool_tmeta is now incomplete Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Zdenek Kabelac Cc: LVM general discussion and development , LVM2 development 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? > 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! Regards, Eric -- - Eric Ren