<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c1">Comment # 1</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 <span class="vcard"><a class="email" href="mailto:kay@vrfy.org" title="Kay Sievers <kay@vrfy.org>"> <span class="fn">Kay Sievers</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=79576#c0">comment #0</a>)
<span class="quote">> udevd skips all /dev/sda{.X} processing (and I speculate that fsck is then
> unable to complete its work as well). Looks like a file lock deadlock
> between fsck and udevd ?</span >
Udev's locking scheme is maybe incompatible with the fsck -l feature
that systemd-fsck requests. (systemd-)sck should stay away from
write-locking the entire disk device it has no business with; we need to
sort that out.
<span class="quote">> In passing also note that it appears that the file close of fd_lock is not
> done if the 'goto skip' path is taken in the udevd.c code above.</span >
Fixed.
Thanks,
Kay</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>