Description of problem: Major number gets ignored. [root@link-08 ~]# lvcreate -L 20M -n major -My --major 222 --minor 111 gfs Logical volume "major" created gfs-major 253 111 L--w 0 1 0 LVM-mlBLc3EbXgmSRUU8IZ5zLN143vKWfAqnFRsxOIpbkMYmzTLtneCEyrlbVwZznXMU *** If this does get fixed, then the major number option needs to be added to the man page. *** Version-Release number of selected component (if applicable): 2.6.17-1.2519.4.18.el5 How reproducible: everytime
*** Bug 165765 has been marked as a duplicate of this bug. ***
*** Bug 473394 has been marked as a duplicate of this bug. ***
This is open for years... In kernel 2.6 specifying major number lost its importance with dynamic major allocated. Can we deprecate this option in lvm2 upstream? I think it is now worth it to support it in kernel anymore.
I believe we just need to document this behavior and close this bug as CANTFIX.
*** Bug 858111 has been marked as a duplicate of this bug. ***
OK, we can just document this a bit more.
Finally, I've added a better check: https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=a7c930b18da8f8179312e395c49f72080edd687e
[0] raw/~ $ lvcreate -l1 -My --minor 10 vg Logical volume "lvol0" created [0] raw/~ $ lvcreate -l1 -My --major 254 --minor 11 vg Ignoring supplied major number - kernel assigns major numbers dynamically. Using major number 253 instead. Logical volume "lvol1" created [0] raw/~ $ lvs -o+major,minor lvol0 vg -wima----- 4.00 253 10 lvol1 vg -wima----- 4.00 253 11
[root@virt-122 ~]# lvcreate -L 20M -n major -My --major 222 --minor 111 vg Ignoring supplied major number - kernel assigns major numbers dynamically. Using major number 252 instead. Logical volume "major" created [root@virt-122 ~]# lvs -o+major,minor vg/major LV VG Attr LSize Origin Snap% Move Log Copy% Convert Maj Min major vg -wima- 20.00M 252 111 Marking VERIFIED with: lvm2-2.02.88-13.el5
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1218.html