Skip to contentSkip to conversation

Breakage with raid in 2.6.11-rc1-mm1 [Regression in mm]

DISCUSSION Reuben Farrelly 1 participant 1 message Jan 16, 2005 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hi,

Quoted 14 lines · Reuben Farrelly
Quoted 12 lines · Andrew Morton
Quoted 2 lines · Reuben Farrelly

Something seems to have broken with 2.6.11-rc1-mm1, which worked ok

with

Quoted 8 lines

2.6.10-mm3.

NET: Registered protocol family 17
Starting balanced_irq
BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.

<snip>

Quoted 31 lines
Quoted 26 lines
Quoted 1 line
Kernel panic - not syncing: VFS: Unable to mount root fs on 

unknown-block(0,0)

Quoted 6 lines

The system is running 5 RAID-1 partitions, and md2 is the root as per grub.conf. Problem seems to be that raid autodetection finds no raid partitions :(

The two ST380013AS SATA drives are detected earlier in the boot, so

I don't

Quoted 1 line

think that's the problem..

hm, the only raidy thing we have in there is the below. Maybe you could try reverting that?

--- 25/drivers/md/raid5.c~raid5-overlapping-read-hack 2005-01-09
22:20:40.211246912 -0800
+++ 25-akpm/drivers/md/raid5.c 2005-01-09 22:20:40.216246152 -0800

(quoted diff) +1 -0
@@ -232,6 +232,7 @@ static struct stripe_head *__find_stripe
 }
 
 static void unplug_slaves(mddev_t *mddev);
+static void raid5_unplug_device(request_queue_t *q);
 
 static struct stripe_head *get_active_stripe(raid5_conf_t *conf, 
 sector_t sector,
Quoted 1 line

int pd_idx, int noblock)

Ok the breakage occurred somewhere between 2.6.10-mm3 (works) and 2.6.11-rc1 (doesn't work) ie wasn't introduced into the latest -mm patchset as I first thought.

Quoted 3 lines

Are there any other patches that might be worth a try backing out?

reuben

I did a full untar of the source and rebuilt my (crusty old) config file from scratch, and it seems to have come right now. Can't really explain it though...but obviously wasn't a problem with the -mm release as I first though. Now running -rc1-mm1 with no problems and no other patches.

Thanks to those who helped on what turned out to be a false alarm.

reuben