<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - udevd flock() failure on disk partitions due to fsck holding WRITE FLOCK" href="https://bugs.freedesktop.org/show_bug.cgi?id=79576#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - udevd flock() failure on disk partitions due to fsck holding WRITE FLOCK" href="https://bugs.freedesktop.org/show_bug.cgi?id=79576">bug 79576</a> from <a class="email" href="mailto:kay@vrfy.org" title="Kay Sievers <kay@vrfy.org>"> Kay Sievers</a> <pre>(In reply to <a href="show_bug.cgi?id=79576#c2">comment #2</a>) Date: Tue, 03 Jun 2014 14:49:38 +0000 > Subject: udev: exclude device-mapper from block device ownership event > locking > > will have no effect for systems which do not use lvm.. which includes mine. It was not intended to fix this. > From additional debugging, for boots where the fscks fail it looks like the > systemd-fsck-root.service starts, invoking fsck -l, which locks the whole > disk, and then systemd-fsck@.service is activated for the various non-root > partitions before systemd-fsck-root.service has completed, whereas, for > boots where all fscks succeed, systemd-fsck-root.service appears to have > completed before the various systemd-fsck@.services are started. fsck from util-linux will be changed to not take write locks on the disk device. We need to disable udev's locking logic, or stop using '-l' until fsck is changed.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>