On Wed, 2007-03-21 at 20:59 +0100, Jens Axboe wrote:
quoted text
> On Wed, Mar 21 2007, Dale Blount wrote:
> > On Wed, 2007-03-21 at 14:09 -0400, Chuck Ebbert wrote:
> > > Dale Blount wrote:
> > > >> I'm puzzled why this is hitting Dan, but no one else has reported
> > > >> anything. Dan, did 2.6.19 work for you?
> > > > 
> > > > Actually, I believe it is happening to me too.  This is on a 4-disk raid5 with
> > > > one failed disk on two 2-port sata_sil pci controller cards.
> > > > 
> > > > The BUG below is from 2.6.20.3, but I will try 2.6.21-rc4 tonight.
> > > > The disk didn't fail until 2.6.20, so I don't know if 2.6.19 would have worked
> > > > or not.
> > > > 
> > > > 
> > > 
> > > Just to be clear: you have a RAID array (what level?) with a failed disk
> > > and it's giving you the same error that Dan gets?
> > 
> > 
> > Yes, the BUG looks to be pretty similar to me.  It's a 4 disk raid5 with
> > one disk missing (dead and sent in for RMA).
> 
> Interesting, I'll definitely see if I can reproduce it like that.
> 

FWIW, the server made it through a round using 2.6.21-rc4 without
errors.  2.6.20.x failed 5 times straight and worked 4 times prior to
that (also with a missing disk), so it could be a coincidence too.

The disk is back from RMA, do you need me to hold off replacing it?

Thanks,

Dale

-
unsubscribe notice
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/