Bug 915941 - udevd gets into an infinite loop trying to create /dev/disk symlinks
Summary: udevd gets into an infinite loop trying to create /dev/disk symlinks
Keywords:
Status: CLOSED DUPLICATE of bug 909826
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-26 20:12 UTC by Daniel Berrangé
Modified: 2013-03-07 13:10 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-07 13:10:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel Berrangé 2013-02-26 20:12:43 UTC
Description of problem:
Frequently when I plug in my (LUKS encrypted) USB memory stick, systemd-udevd seems to get itself into an infinite loop, filling dmesg logs with the following

[40541.715156] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.715349] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.715544] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.715739] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.715878] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk: File exists
[40541.716232] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.716428] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.717882] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk: File exists
[40541.718112] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk: File exists
[40541.718174] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.718364] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.718552] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.718743] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.718935] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.719215] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.719359] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk: File exists
[40541.719417] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.719609] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.721780] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.721973] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.722209] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.722401] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists
[40541.722556] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk: File exists
[40541.722749] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk: File exists
[40541.723974] systemd-udevd[11549]: Failed to set security context (null) for /dev/disk/by-path: File exists

the USB disk never gets mounted. Unplugging & plugging back in the USB disk does not make any difference. The only solution I've found is to kill the systemd-udevd process & let it be re-started by systemd. It'll then work fine for a (unknown) period of time, when the problem will occur again.


Version-Release number of selected component (if applicable):
systemd-197-1.fc18.1.x86_64

How reproducible:
Often, but not always

Steps to Reproduce:
1. Plug in a USB memory stick (not sure if it having LUKS encryption is relevant)
2.
3.
  
Actual results:
The disk never gets mounted, and the logs fill with the messages shown above

Expected results:
The disk is mounted & accessible to my desktop user

Additional info:

Comment 1 Lennart Poettering 2013-03-07 13:10:54 UTC

*** This bug has been marked as a duplicate of bug 909826 ***


Note You need to log in before you can comment on or make changes to this bug.