Bug 1114770

Summary: internal SATA SSD as mpathc instead of sda
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: agk, amulhern, anaconda-maint-list, bcl, bmarzins, dlehman, dwysocha, fdinitto, heinzm, lvm-team, msnitzer, prajnoha, prockai, vpodzime, zkabelac
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:52:41 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:
Embargoed:
Attachments:
Description Flags
dmesg
none
journalctl -l -b -o short-monotonic
none
anaconda storage.log none

Description Chris Murphy 2014-06-30 23:17:20 UTC
Description of problem: The installer reports the SATA SSD device I'm going to install do is at /dev/mapper/mpathc rather than /dev/sda. This could be a device-mapper or kernel bug, not sure, but it manifests so far only in the Live environment when doing an OS install, not in the installed environment.


Version-Release number of selected component (if applicable):
python-blivet-0.59-1.fc21.noarch
device-mapper-1.02.86-1.fc21.x86_64
anaconda-21.45-1.fc21.x86_64


How reproducible:
Non-deterministic, but happens often.

Steps to Reproduce:
1. Launch anaconda and go through an installation.
2.
3.

Actual results:
In various parts of the UI, the installer refers to the target device as mpathc.

Expected results:
Target device should be sda.

Additional info:

Comment 1 Chris Murphy 2014-06-30 23:21:44 UTC
Created attachment 913585 [details]
dmesg

OK at 17 seconds monotonic time a preexisting sda6 swap partition is referred to by systemd as /dev/mapper/mapthc6. So this bug is set to the wrong component. No idea if it's a systemd, systemd-udev, or device-mapper bug.

Comment 2 Chris Murphy 2014-06-30 23:22:26 UTC
Created attachment 913586 [details]
journalctl -l -b -o short-monotonic

Comment 3 Chris Murphy 2014-06-30 23:23:29 UTC
Created attachment 913587 [details]
anaconda storage.log

Comment 4 Brian Lane 2014-07-01 00:21:41 UTC
[   13.000642] rawhide.localdomain multipathd[789]: sda: add path (uevent)
[   13.001228] rawhide.localdomain multipathd[789]: sda: spurious uevent, path already in pathvec
[   13.048938] rawhide.localdomain kernel: device-mapper: multipath service-time: version 0.2.0 loaded
[   13.013270] rawhide.localdomain multipathd[789]: mpathc: load table [0 500118192 multipath 0 0 1 1 service-time 0 1 1 8:0 1]
[   13.013779] rawhide.localdomain multipathd[789]: mpathc: event checker started
[   13.014108] rawhide.localdomain multipathd[789]: sda [8:0]: path added to devmap mpathc

would seem to indicate multipathd.

Comment 5 Chris Murphy 2014-07-01 02:37:34 UTC
Yeah if I find the wwid with multipath -v2 and blacklist it in multipath.conf I don't run into this, the SSD appears in anaconda normally as expected. Also sometimes causes anaconda to bogusly claim no disks are found: see dup bug 1114783 for that manifestation.

Comment 6 Brian Lane 2014-07-01 15:25:01 UTC
*** Bug 1114783 has been marked as a duplicate of this bug. ***

Comment 7 Chris Murphy 2014-10-28 16:57:55 UTC
I haven't experienced this in over a month, but don't know if that means something was found and fixed, or if the problem's just become much more rare.

Comment 8 Jaroslav Reznik 2015-03-03 16:05:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 9 Fedora End Of Life 2016-07-19 11:52:41 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.