> On Fri, 2005-09-16 at 11:28 -0500, Hongwei Li wrote: >> > Hongwei Li wrote: >> >> I updated selinux-policy-targeted from 1.23.16-6 to 1.25.4-10.1, then >> >> service >> >> dovecot can start without error. However, booting process still shows >> >> error: >> >> >> >> Setting up Logical Volume Management: /var/lock mkdir failed, read-only >> >> filesystem >> >> >> >> Setting selinux default as permissive, then reboot, still get the same >> >> error. >> >> So, this one is not selinux issue. Then, what does it actually mean? How >> to >> >> fix it? BTW, I reinstalled FC4 twice, the same situation. >> > >> > I think you may be able to ignore this one. When rc.sysinit is doing >> > "Setting up Logical Volume Management", it runs lvm with the >> > --ignorelockingfailure option (see "man lvm") because everything is >> > initially mounted read-only and locks can't be set. So although the >> > error message is generated, booting proceeds as normal. >> > >> > Paul. >> > >> >> Thanks! That makes me easy. However, I wonder if everybody gets this same >> error or not. If yes, then why fc4 release can't fix this issue? (fc4 is >> not >> released recently). If not, why just me getting this error. Since I am >> going >> to run/install many other packages (I haven't done anything else), I am >> worried about this problem. Hope it will not cause any new problem. >> >> Thanks! >> >> Hongwei >> > > Report it as a bug to bugzilla. IIRC: The error also occurs in > rawhide. > > Bob... > > -- How to report it to bugzilla? I never used it. Thanks! Hongwei
