Description of problem: When booting a RHEL5.6 box just updated from 5.5 I see the following message: Setting up Logical Volume Management: File-based locking initialisation failed. Version-Release number of selected component (if applicable): RHEL5.6, lvm2-2.02.74-5.el5, initscripts-8.45.33-1.el5 How reproducible: Every time. Steps to Reproduce: 1. Update to the above two packages 2. Reboot 3. Watch the boot scroll Actual results: Machine still boots, but message is worrying. Expected results: No warning message. Additional info: I believe this is connected with https://bugzilla.redhat.com/show_bug.cgi?id=566010 and is probably something to do with a regression in lvm which is now failing to honour "--ignorelockingfailure" in /etc/rc.d/rc.sysinit.
Yes, the problem is with /sbin/lvm.static vgchange -a y --ignorelockingfailure in initscripts. New systems uses --sysinit here, RHEL5 need to keep backward compatibility. It is just about suppressing error message, system should still work without problem. So there are two possible solutions - madify initscripts or - patch lvm2 for rhel5 only to handle --initlockingfailure quietly.
Because RHEL5 initscripts should be backward compatible I would prefer this simple change in lvm2 to suppress these messages. (All new distros use sysinit switch already.) --- LVM2.2.02.74.old/tools/lvmcmdline.c 2011-01-24 15:08:27.000000000 +0100 +++ LVM2.2.02.74/tools/lvmcmdline.c 2011-01-24 15:09:57.496223486 +0100 @@ -1074,7 +1074,8 @@ int lvm_run_command(struct cmd_context * else locking_type = -1; - if (!init_locking(locking_type, cmd, arg_count(cmd, sysinit_ARG))) { + if (!init_locking(locking_type, cmd, arg_count(cmd, ignorelockingfailure_ARG) || + arg_count(cmd, sysinit_ARG))) { ret = ECMD_FAILED; goto out; }
Fixed in lvm2-2.02.74-6.el5.
Fix verified in lvm2-2.02.84-3.el5. I saw the error when going from RHEL5.5 -> lvm2-2.02.74-5.el5: Setting up Logical Volume Management: File-based locking initialisation failed. But not when going from RHEL5.5 -> lvm2-2.02.84-3.el5: Setting up Logical Volume Management: loop: loaded (max 8 devices)
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: This field is the basis of the errata or release note for this bug. It can also be used for change logs. The Technical Note template, known as CCFR, is as follows: Cause What actions or circumstances cause this bug to present. Consequence What happens when the bug presents. Fix What was done to fix the bug. Result What now happens when the actions or circumstances above occur. Note: this is not the same as the bug doesn’t present anymore.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1071.html