Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261964AbVANMSx (ORCPT ); Fri, 14 Jan 2005 07:18:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261966AbVANMSx (ORCPT ); Fri, 14 Jan 2005 07:18:53 -0500 Received: from tornado.reub.net ([60.234.136.108]:41936 "EHLO tornado.reub.net") by vger.kernel.org with ESMTP id S261964AbVANMSt (ORCPT ); Fri, 14 Jan 2005 07:18:49 -0500 Message-Id: <6.2.0.14.2.20050115011704.01da8ec8@tornado.reub.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Sat, 15 Jan 2005 01:18:46 +1300 To: Andrew Morton From: Reuben Farrelly Subject: Re: Breakage with raid in 2.6.11-rc1-mm1 [Regression in mm] Cc: linux-kernel@vger.kernel.org, Neil Brown In-Reply-To: <20050114035852.3b5ff1a3.akpm@osdl.org> References: <6.2.0.14.2.20050114233439.01cbb8d8@tornado.reub.net> <20050114035852.3b5ff1a3.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2689 Lines: 72 At 12:58 a.m. 15/01/2005, Andrew Morton wrote: >Reuben Farrelly 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) It's not that patch...with it reverted as above, it I'm still seeing the same problem. I'll give a generic 2.6.11-rc1 a try and see if the problem is in there also. Reuben - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/