Bug 1308292

Summary:	duplicate device message in sysfs from systemd
Product:	[Fedora] Fedora	Reporter:	George R. Goffe <grgoffe>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	22	CC:	johannbg, lnykryn, msekleta, muadda, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 19:24:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description George R. Goffe 2016-02-14 00:37:58 UTC

Description of problem:

This problem just started happening a couple of days ago.

Feb 13 16:20:17 fc22 systemd[1]: Device dev-sdb1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb2/2-1/2-1.3/2-1.3:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1 and /sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb2/2-1/2-1.3/2-1.3:1.0/host10/target10:0:0/10:0:0:0/block/sdb/sdb1

Version-Release number of selected component (if applicable):

systemd-219-27.fc22.x86_64

How reproducible:

unknown

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fedora End Of Life 2016-07-19 19:24:44 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.