Description of problem: Unable to set the minor number of an LV to someting above 255 Version-Release number of selected component (if applicable): This happens in RHEL 5.7, 5.8, 6.2, and 6.3 How reproducible: 100% Steps to Reproduce: 1. lvchange --persistent y --major 253 --minor 265 ANY_LV Actual results: Minor number outside range 0-255 Invalid argument for --minor: 265 Error during parsing of command line. Expected results: The persistent minor number should be set to 265 Additional info:
Amazing nobody did hit this before! But yes, it's a bug (we still need to check for the kernel and metadata version though).
New limit set to follow the kernel >= 2.6: 12 and 20 bits for major and minor number (4095 and 1048575). http://git.fedorahosted.org/cgit/lvm2.git/commit/?id=6e55201144be3bcf82b6aafe7e9f7430318719d0
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Tested and setting up a high-numbered minor works with lvm2-2.02.88-11.el5 (04:46:51) [root@r5-node02:~]$ lvchange --persistent y --major 252 --minor 300 test/majnor Logical volume majnor will be deactivated temporarily. Continue? [y/n]: y Logical volume "majnor" changed (04:47:16) [root@r5-node02:~]$ dmsetup ls VolGroup00-LogVol01 (252, 1) VolGroup00-LogVol00 (252, 0) test-majnor (252, 300)
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-2013-1352.html