Bug 701080 - mdadm will not assemble specific raid1 in 2.6.35.12-90.fc14.x86_64. Works fine in 2.6.35.10-74.fc14.x86_64
mdadm will not assemble specific raid1 in 2.6.35.12-90.fc14.x86_64. Works fin...
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: mdadm (Show other bugs)
14
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Jes Sorensen
Nobody's working on this, feel free to take it
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-30 18:55 EDT by bugzilla
Modified: 2012-05-10 15:10 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-10 15:10:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description bugzilla 2011-04-30 18:55:32 EDT
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.57 Safari/534.24

running kernel 2.6.35.10-74.fc14.x86_64 mdadm works fine on all arrays
running kernel 2.6.35.12-90.fc14.x86_64 mdadm works fine on all arrays EXCEPT one

output from /var/log/messages on kernel 2.6.35.10-74.fc14.x86_64 (The one that works):

Apr 30 23:43:31 fc14 kernel: [   10.903140] md: bind<sdd1>
Apr 30 23:43:31 fc14 kernel: [   10.904190] md: bind<sdc1>
Apr 30 23:43:31 fc14 kernel: [   10.906675] md/raid1:md21: active with 2 out of 2 mirrors
Apr 30 23:43:31 fc14 kernel: [   10.906690] md21: detected capacity change from 0 to 2000397795328
Apr 30 23:43:31 fc14 kernel: [   10.914434]  md21: unknown partition table


output from /var/log/messages on kernel  2.6.35.12-90.fc14.x86_64 (The one that does NOT work):


Apr 30 16:23:38 fc14 kernel: [    7.350145] md: md21 stopped.
Apr 30 16:23:38 fc14 kernel: [    7.351067] dracut: mdadm: WARNING /dev/sdd1 and /dev/sdd appear to have very similar superblocks.
Apr 30 16:23:38 fc14 kernel: [    7.351113] dracut: If they are really different, please --zero the superblock on one
Apr 30 16:23:38 fc14 kernel: [    7.351155] dracut: If they are the same or overlap, please remove one from the
Apr 30 16:23:38 fc14 kernel: [    7.351182] dracut: DEVICE list in mdadm.conf.
...
...

Apr 30 16:23:38 fc14 kernel: [    7.764937] md: md21 stopped.
Apr 30 16:23:38 fc14 kernel: [    7.765906] dracut: mdadm: WARNING /dev/sdc1 and /dev/sdc appear to have very similar superblocks.
Apr 30 16:23:38 fc14 kernel: [    7.765951] dracut: If they are really different, please --zero the superblock on one
Apr 30 16:23:38 fc14 kernel: [    7.765994] dracut: If they are the same or overlap, please remove one from the
Apr 30 16:23:38 fc14 kernel: [    7.766022] dracut: DEVICE list in mdadm.conf.


Reproducible: Always

Steps to Reproduce:
1. Install kernel 2.6.35.12-90.fc14.x86_64
2. Boot the PC
3.
Actual Results:  
Raid1 /dev/md21 is not created
/dev/sdc1 does not exist
/dev/sdd1 does not exist


Expected Results:  
I would have expected that /dev/md21 was created
I would have expected that /dev/sdc1 did exist
I would have expected that /dev/sdd1 did exist


output from /var/log/messages on kernel 2.6.35.10-74.fc14.x86_64 (The one that works):

Apr 30 23:43:31 fc14 kernel: [    2.915030] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 30 23:43:31 fc14 kernel: [    2.916396] ata3.00: ATA-8: Hitachi HDS722020ALA330, JKAOA3MA, max UDMA/133
Apr 30 23:43:31 fc14 kernel: [    2.916399] ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
Apr 30 23:43:31 fc14 kernel: [    2.917907] ata3.00: configured for UDMA/133
Apr 30 23:43:31 fc14 kernel: [    2.928085] scsi 2:0:0:0: Direct-Access     ATA      Hitachi HDS72202 JKAO PQ: 0 ANSI: 5
Apr 30 23:43:31 fc14 kernel: [    2.928195] sd 2:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Apr 30 23:43:31 fc14 kernel: [    2.928218] sd 2:0:0:0: Attached scsi generic sg2 type 0
Apr 30 23:43:31 fc14 kernel: [    2.928235] sd 2:0:0:0: [sdc] Write Protect is off
Apr 30 23:43:31 fc14 kernel: [    2.928257] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 30 23:43:31 fc14 kernel: [    2.928373]  sdc: sdc1
Apr 30 23:43:31 fc14 kernel: [    2.930839] sd 2:0:0:0: [sdc] Attached SCSI disk
Apr 30 23:43:31 fc14 kernel: [    3.806020] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 30 23:43:31 fc14 kernel: [    3.807390] ata4.00: ATA-8: Hitachi HDS722020ALA330, JKAOA3MA, max UDMA/133
Apr 30 23:43:31 fc14 kernel: [    3.807393] ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
Apr 30 23:43:31 fc14 kernel: [    3.808900] ata4.00: configured for UDMA/133
Apr 30 23:43:31 fc14 kernel: [    3.819087] scsi 3:0:0:0: Direct-Access     ATA      Hitachi HDS72202 JKAO PQ: 0 ANSI: 5
Apr 30 23:43:31 fc14 kernel: [    3.819198] sd 3:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Apr 30 23:43:31 fc14 kernel: [    3.819215] sd 3:0:0:0: Attached scsi generic sg3 type 0
Apr 30 23:43:31 fc14 kernel: [    3.819238] sd 3:0:0:0: [sdd] Write Protect is off
Apr 30 23:43:31 fc14 kernel: [    3.819259] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 30 23:43:31 fc14 kernel: [    3.819370]  sdd: sdd1
Apr 30 23:43:31 fc14 kernel: [    3.820899] sd 3:0:0:0: [sdd] Attached SCSI disk



output from /var/log/messages on kernel  2.6.35.12-90.fc14.x86_64 (The one that does NOT work):


Apr 30 16:23:38 fc14 kernel: [    2.916014] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 30 16:23:38 fc14 kernel: [    2.917379] ata3.00: ATA-8: Hitachi HDS722020ALA330, JKAOA3MA, max UDMA/133
Apr 30 16:23:38 fc14 kernel: [    2.917383] ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
Apr 30 16:23:38 fc14 kernel: [    2.918885] ata3.00: configured for UDMA/133
Apr 30 16:23:38 fc14 kernel: [    2.929090] scsi 2:0:0:0: Direct-Access     ATA      Hitachi HDS72202 JKAO PQ: 0 ANSI: 5
Apr 30 16:23:38 fc14 kernel: [    2.929198] sd 2:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Apr 30 16:23:38 fc14 kernel: [    2.929216] sd 2:0:0:0: Attached scsi generic sg2 type 0
Apr 30 16:23:38 fc14 kernel: [    2.929239] sd 2:0:0:0: [sdc] Write Protect is off
Apr 30 16:23:38 fc14 kernel: [    2.929261] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 30 16:23:38 fc14 kernel: [    2.929378]  sdc: sdc1
Apr 30 16:23:38 fc14 kernel: [    2.936486] sd 2:0:0:0: [sdc] Attached SCSI disk
Apr 30 16:23:38 fc14 kernel: [    3.807014] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 30 16:23:38 fc14 kernel: [    3.808379] ata4.00: ATA-8: Hitachi HDS722020ALA330, JKAOA3MA, max UDMA/133
Apr 30 16:23:38 fc14 kernel: [    3.808383] ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
Apr 30 16:23:38 fc14 kernel: [    3.809885] ata4.00: configured for UDMA/133
Apr 30 16:23:38 fc14 kernel: [    3.820086] scsi 3:0:0:0: Direct-Access     ATA      Hitachi HDS72202 JKAO PQ: 0 ANSI: 5
Apr 30 16:23:38 fc14 kernel: [    3.820198] sd 3:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Apr 30 16:23:38 fc14 kernel: [    3.820213] sd 3:0:0:0: Attached scsi generic sg3 type 0
Apr 30 16:23:38 fc14 kernel: [    3.820238] sd 3:0:0:0: [sdd] Write Protect is off
Apr 30 16:23:38 fc14 kernel: [    3.820263] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 30 16:23:38 fc14 kernel: [    3.820376]  sdd: sdd1
Apr 30 16:23:38 fc14 kernel: [    3.827600] sd 3:0:0:0: [sdd] Attached SCSI disk
Comment 1 Doug Ledford 2012-05-10 15:06:48 EDT
This is a stale bug.  I'm not sure if we are even supporting fc14 any more.  Jes, if we aren't doing fc14 any more, then likely this just needs closed out.
Comment 2 Jes Sorensen 2012-05-10 15:10:56 EDT
Fedora 14 is end of life unfortunately and we can no longer push fixes out
for it.

If you can reproduce this in Fedora 15 or preferably Fedora 16 or 17, please
open a new bug.

Cheers,
Jes

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