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

[Reuben Farrelly]

At 12:58 a.m. 15/01/2005, Andrew Morton wrote:
> Reuben Farrelly <reuben-lkml@xxxxxxxx> wrote:
> >
> > Something seems to have broken with 2.6.11-rc1-mm1, which worked ok with
> > 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.
> > VFS: Waiting 19sec for root device...
> > VFS: Waiting 18sec for root device...
> > VFS: Waiting 17sec for root device...
> > VFS: Waiting 16sec for root device...
> > VFS: Waiting 15sec for root device...
> > VFS: Waiting 14sec for root device...
> > VFS: Waiting 13sec for root device...
> > VFS: Waiting 12sec for root device...
> > VFS: Waiting 11sec for root device...
> > VFS: Waiting 10sec for root device...
> > VFS: Waiting 9sec for root device...
> > VFS: Waiting 8sec for root device...
> > VFS: Waiting 7sec for root device...
> > VFS: Waiting 6sec for root device...
> > VFS: Waiting 5sec for root device...
> > VFS: Waiting 4sec for root device...
> > VFS: Waiting 3sec for root device...
> > VFS: Waiting 2sec for root device...
> > VFS: Waiting 1sec for root device...
> > VFS: Cannot open root device "md2" or unknown-block(0,0)
> > Please append a correct "root=" boot option
> > Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(0,0)
> >
> > 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
> > 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
> @@ -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,
>                                              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.

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

reuben

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/