Bug 1018272
Summary: | md devices get incorrect names, system stops booting | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Woodhouse <dwmw2> |
Component: | kernel | Assignee: | Jes Sorensen <Jes.Sorensen> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | agk, gansalmon, harald, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa, prajnoha, ta.chang1972 |
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: | 2013-10-14 13:57:54 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: |
Description
David Woodhouse
2013-10-11 15:22:32 UTC
This sounds familiar, but I don't recall why and I can't find a previous bug that matches this. David noted in IRC that both dracut and mdadm were updated as well. David, Can you provide the following info please: mdadm version /proc/mdstat out mdadm --examine </dev/sdX> output of the devices of the arrays Thanks, Jes Under the 3.10.14-100 kernel: [root@twosheds ~]# mdadm --examine /dev/sda1 /dev/sda1: Magic : a92b4efc Version : 0.90.00 UUID : 20166bf1:24f712c0:57559a00:6d37fb89 Creation Time : Thu Jul 3 03:29:41 2008 Raid Level : raid1 Used Dev Size : 506816 (495.02 MiB 518.98 MB) Array Size : 506816 (495.02 MiB 518.98 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 125 Update Time : Sun Oct 13 01:00:06 2013 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 4d944be9 - correct Events : 2010 Number Major Minor RaidDevice State this 1 8 1 1 active sync /dev/sda1 0 0 8 17 0 active sync /dev/sdb1 1 1 8 1 1 active sync /dev/sda1 [root@twosheds ~]# mdadm --examine /dev/sdb1 /dev/sdb1: Magic : a92b4efc Version : 0.90.00 UUID : 20166bf1:24f712c0:57559a00:6d37fb89 Creation Time : Thu Jul 3 03:29:41 2008 Raid Level : raid1 Used Dev Size : 506816 (495.02 MiB 518.98 MB) Array Size : 506816 (495.02 MiB 518.98 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 125 Update Time : Sun Oct 13 01:00:06 2013 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 4d944bf7 - correct Events : 2010 Number Major Minor RaidDevice State this 0 8 17 0 active sync /dev/sdb1 0 0 8 17 0 active sync /dev/sdb1 1 1 8 1 1 active sync /dev/sda1 As described in comment 0, running 'mdadm --examine' under the older kernel (with the initramfs which was build with older mdadm and dracut) shows *different* results for 'Preferred Minor'. Ok, So old 0.9 metadata arrays. This does sound a bit similar to BZ#1015204 where mdadm.conf isn't copied into the initramfs and dracut assembles the arrays as it sees fit. I am not sure whether dracut respects the preferred minor number in the superblock when assembling the array. Harald, do you have any input on this? Thanks, Jes Indeed, if I unpack each initramfs image, only the old one has a copy of mdadm.conf But why would it not respect the preferred minor number? And why in $DEITY's name is the preferred minor number *different* under different kernels? When we boot the new kernel/initramfs, does it not only ignore the preferred minor but also *update* the preferred minor in each individual device of the array to match the new numbers it pulled out of its posterior? What happens if you manually add the mdadm.conf to the initramfs? Do you get the old behaviour back? The preferred minor number is just a hint and not guaranteed for anything. In fact, there is no such thing in v1.2 metadata superblocks, not sure about v1.0/v1.1 Then again, I suspect this is happening in dracut/mdadm not in the kernel. I don't know if dracut explicitly picks a device name when it assembles the array or if it relies on mdadm for picking one for it. Looks like this is a dupe of 1015204 *** This bug has been marked as a duplicate of bug 1015204 *** *** Bug 1020134 has been marked as a duplicate of this bug. *** I'm a person who encountered the same issue as this and had already reported in duplicate bug of 1020134. Although I don't know it is real reference of this report very much, I've tried to renew existed initramfs with dracut --force option. But no luck has come... |