linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Gang He" <ghe@suse.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvmetad cannot handle md device with big minor number
Date: Mon, 24 Dec 2018 22:52:48 -0700	[thread overview]
Message-ID: <5C21C5B0020000F90004A3CB@prv1-mh.provo.novell.com> (raw)

Hello Guys,

I create a md device with a big minor number, and add this md device as PV disk.
Then, pvdisplay can not display this PV.
But, if I disable lvmetad via changing the configuration setting "use_lvmetad = 1" to "use_lvmetad = 0",
pvdisplay can display this PV, then I can do the next things, e.g. create a VG on this PV, etc.
It looks that lvmetad cannot handle md device with big minor number (e.g. /dev/md606099).
If I create a md device like "/dev/md0", lvmetad can work.

The whole reproduce steps are as below,
1) # mdadm -C /dev/md606099 -l 1 -n 2 /dev/sdb2 /dev/sda2

2) # pvcreate /dev/md606099
  Physical volume "/dev/md606099" successfully created.
    # lsblk
NAME         MAJ:MIN    RM  SIZE RO TYPE  MOUNTPOINT
sda            8:0       0  160G  0 disk
├─sda1         8:1       0  120G  0 part
├─sda2         8:2       0   30G  0 part
│ └─md606099   9:606099  0   30G  0 raid1
└─sda3         8:3       0   10G  0 part
sdb            8:16      0  500G  0 disk
├─sdb1         8:17      0  120G  0 part
├─sdb2         8:18      0   30G  0 part
│ └─md606099   9:606099  0   30G  0 raid1
└─sdb3         8:19      0  350G  0 part

3) # pvdisplay
  WARNING: Device for PV GIAOmw-SOu7-8ZaH-qWBw-MwfR-Jb6j-wxSM1a not found or rejected by a filter. <<== here, the PV
can not be displayed

4) # lvm version
  LVM version:     2.02.180(2) (2018-07-19)
  Library version: 1.03.01 (2018-07-19)
  Driver version:  4.39.0
  Configuration:   ./configure --host=x86_64-suse-linux-gnu --build=x86_64-suse-linux-gnu --program-prefix=
--disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/lib --localstatedir=/var
--sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --disable-dependency-tracking
--enable-dmeventd --enable-cmdlib --enable-udev_rules --enable-udev_sync --with-udev-prefix=/usr/ --enable-selinux
--enable-pkgconfig --with-usrlibdir=/usr/lib64 --with-usrsbindir=/usr/sbin --with-default-dm-run-dir=/run
--with-tmpfilesdir=/usr/lib/tmpfiles.d --with-thin=internal --with-device-gid=6 --with-device-mode=0640
--with-device-uid=0 --with-dmeventd-path=/usr/sbin/dmeventd --with-thin-check=/usr/sbin/thin_check
--with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair --enable-applib --enable-blkid_wiping
--enable-cmdlib --enable-lvmetad --enable-lvmpolld --enable-realtime --with-cache=internal
--with-default-locking-dir=/run/lock/lvm --with-default-pid-dir=/run --with-default-run-dir=/run/lvm --enable-cmirrord

5) # tb1213-nd1:/sys/dev/block # ll
total 0
lrwxrwxrwx 1 root root 0 Dec 25 13:35 11:0 ->
../../devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0
lrwxrwxrwx 1 root root 0 Dec 25 13:35 253:0 -> ../../devices/pci0000:00/0000:00:04.0/virtio1/block/vda
lrwxrwxrwx 1 root root 0 Dec 25 13:35 253:1 -> ../../devices/pci0000:00/0000:00:04.0/virtio1/block/vda/vda1
lrwxrwxrwx 1 root root 0 Dec 25 13:35 253:2 -> ../../devices/pci0000:00/0000:00:04.0/virtio1/block/vda/vda2
lrwxrwxrwx 1 root root 0 Dec 25 13:35 253:3 -> ../../devices/pci0000:00/0000:00:04.0/virtio1/block/vda/vda3
lrwxrwxrwx 1 root root 0 Dec 25 13:35 8:0 -> ../../devices/platform/host2/session1/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Dec 25 13:35 8:1 -> ../../devices/platform/host2/session1/target2:0:0/2:0:0:0/block/sda/sda1
lrwxrwxrwx 1 root root 0 Dec 25 13:35 8:16 -> ../../devices/platform/host2/session1/target2:0:0/2:0:0:1/block/sdb
lrwxrwxrwx 1 root root 0 Dec 25 13:35 8:17 -> ../../devices/platform/host2/session1/target2:0:0/2:0:0:1/block/sdb/sdb1
lrwxrwxrwx 1 root root 0 Dec 25 13:35 8:18 -> ../../devices/platform/host2/session1/target2:0:0/2:0:0:1/block/sdb/sdb2
lrwxrwxrwx 1 root root 0 Dec 25 13:35 8:19 -> ../../devices/platform/host2/session1/target2:0:0/2:0:0:1/block/sdb/sdb3
lrwxrwxrwx 1 root root 0 Dec 25 13:35 8:2 -> ../../devices/platform/host2/session1/target2:0:0/2:0:0:0/block/sda/sda2
lrwxrwxrwx 1 root root 0 Dec 25 13:35 8:3 -> ../../devices/platform/host2/session1/target2:0:0/2:0:0:0/block/sda/sda3
lrwxrwxrwx 1 root root 0 Dec 25 13:35 9:606099 -> ../../devices/virtual/block/md606099   <<== this md device

Thanks
Gang

                 reply	other threads:[~2018-12-25  5:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5C21C5B0020000F90004A3CB@prv1-mh.provo.novell.com \
    --to=ghe@suse.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).