Hide Forgot
Description of problem: LVM appears to have a name limit for the vg name of 127 characters. However, if you create a vg with a name this long you cannot create any LVs in it. Version-Release number of selected component (if applicable): NA How reproducible: All the time Steps to Reproduce: 1. Create a VG with a max length name # vgcreate 'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz' /dev/sdd Volume group "zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz" successfully created 2. Try to create a LV in the VG # lvcreate -L16m -n a zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz Internal error: LV name "zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz/a" length 131 is not supported. Actual results: Unable to create LV Expected results: Ability to create a LV in a VG that was just created if you conform to the limits. Additional info: The error message "length 131 is not supported" seems confusing as the returned string in error message is only 129 characters. If the real limit is the vg name + lv name, shouldn't we make the max vg name shorter to allow LVs to be created?
The limitation applies to whole device name - 128chars + \0 So it's "vgname '-' lvname" with all its mangling which needs to fit the limits. (i.e. if name has '-' inside - it's doubled) Yep - it's known issue for long time we do not properly validate all cases at the right time - currently seen as low-prio bug. vgname is basically 'integral' subpart of the whole LV name. (some does applyto UUID where you have prefix + vguuid + lvuuid + suffix).
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.