Red Hat Bugzilla – Bug 510605
endian issues with RAID UUID on ppc
Last modified: 2014-03-16 23:19:22 EDT
Description of problem:
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3d33116f:1853b1a7:00cf57ef:cb11dcaa
mdadm -E of component device:
Magic : a92b4efc
Version : 0.90.00
UUID : 6f11333d:a7b15318:ef57cf00:aadc11cb (local to host localhost.localdomain)
Creation Time : Mon Jul 6 08:04:43 2009
Raid Level : raid1
Used Dev Size : 17775552 (16.95 GiB 18.20 GB)
Array Size : 17775552 (16.95 GiB 18.20 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Mon Jul 6 08:28:57 2009
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : efd4c906 - correct
Events : 6
Number Major Minor RaidDevice State
this 1 8 17 1 active sync /dev/sdb1
0 0 8 3 0 active sync /dev/sda3
1 1 8 17 1 active sync /dev/sdb1
Version-Release number of selected component (if applicable):
RHEL 6 alpha
Steps to Reproduce:
1. Install RAID1.
fsck fails, as mdadm doesn't activate the device.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
mdadm is broken on ppc, and has been ever since 3.0 landed in February.
Fixed in 3.0-0.devel3.8.el6.
Fixed in 'mdadm-3.0-0.devel3.8.el6'. 'mdadm-3.0.2-1.el6' included in compose 'RHEL6.0-20091029.0'.
Moving to ON_QA.
This needs extra special QA love. I have attempted, for hours on end, to reproduce this bug both with the original packages that Bill was using when he reported this bug and with current packages, and I have been unable to reproduce this under any conditions with either ppc or ppc64 hardware. I'm am not convinced that this bug represents the true state of things. However, this bug rendered raid installs on ppc hardware completely DOA on first reboot, so testing that it hasn't come back should be easy. As a result of the ease of verification, I'm removing the patch that went into 3.0-0.devel3.8 entirely because I can not prove that A) it helps or B) is needed and I don't want it cluttering up the package unnecessarily.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.