Summary: | sys-apps/systemd and sys-fs/udev with sys-fs/multipath-tools-0.5.0-r1 - systemd-udevd: Unable to flock(/dev/sda), skipping event handling: Resource temporarily unavailable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander E. Patrakov <patrakov> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | systemd, udev-bugs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://lists.freedesktop.org/archives/systemd-devel/2014-October/024572.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexander E. Patrakov
2014-10-27 19:26:41 UTC
I assume this is also a problem for sys-fs/udev. I have tried to ping upstream about this, unsuccessfully. Fedora applies some 100 patches over inactive multipath-tools upstream package: http://pkgs.fedoraproject.org/cgit/device-mapper-multipath.git/tree/ So, I'm not exectly suprised our package is screwed in multiple ways. Fixed in tree: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e78d65c9e9ffa54a6bece600c8d09881361c4889 I have looked through the commit log of the upstream project, and the code that calls flock(), and found nothing that would explain the "fixed" status. flock() is still called on block devices, and I found nothing that would tell udev to retry. Could you please explain what are you basing your "this is fixed" claim on? P.S. I have not tested the new version either, so it may indeed be fixed. Upstream has included many of those fedora patches, so I presumed it was imported there. I think the bug more relies with dracut in this case. If it is starting multipathd, it should be using the multipath devices (/dev/mapper/...) and not the locked child devices (/dev/sda) Closing this as RESOLVED/UPSTREAM since it was never a Gentoo-specific bug in the first place. |