[systemd-bugs] [Bug 79576] udevd flock() failure on disk partitions due to fsck holding WRITE FLOCK

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79576

--- Comment #4 from Kay Sievers <kay at vrfy.org> ---
(In reply to comment #2)
 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 at .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 at .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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140604/3c0c2165/attachment.html>