Re: md: md6_raid5 crash 2.6.20

2007-02-13 Thread Neil Brown
On Monday February 12, [EMAIL PROTECTED] wrote: > >However > >this "kernel BUG" is something newly introduced in 2.6.20 which should > >be fixed in 2.6.20.1. Patch is below. > > I am using raid6. Am I at risk after applying this patch? I'm not going to say "you are not at risk after applying thi

Re: md: md6_raid5 crash 2.6.20

2007-02-12 Thread Andrew Burgess
>However >this "kernel BUG" is something newly introduced in 2.6.20 which should >be fixed in 2.6.20.1. Patch is below. I am using raid6. Am I at risk after applying this patch? Thanks for your time! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a mess

Re: md: md6_raid5 crash 2.6.20

2007-02-11 Thread Neil Brown
On Monday February 12, [EMAIL PROTECTED] wrote: > > Thanks for the quick response Neil unfortunately the kernel doesn't build with > this patch due to a missing symbol: > > WARNING: "blk_recount_segments" [drivers/md/raid456.ko] undefined! > > Is that in another file that needs patching or withi

Re: md: md6_raid5 crash 2.6.20

2007-02-11 Thread Marc Marais
On Mon, 12 Feb 2007 09:02:33 +1100, Neil Brown wrote > On Sunday February 11, [EMAIL PROTECTED] wrote: > > Greetings, > > > > I've been running md on my server for some time now and a few days ago one > > of > > the (3) drives in the raid5 array starting giving read errors. The result > > was >

Re: md: md6_raid5 crash 2.6.20

2007-02-11 Thread Neil Brown
On Sunday February 11, [EMAIL PROTECTED] wrote: > Greetings, > > I've been running md on my server for some time now and a few days ago one of > the (3) drives in the raid5 array starting giving read errors. The result was > usually system hangs and this was with kernel 2.6.17.13. I upgraded to th

md: md6_raid5 crash 2.6.20

2007-02-10 Thread Marc Marais
Greetings, I've been running md on my server for some time now and a few days ago one of the (3) drives in the raid5 array starting giving read errors. The result was usually system hangs and this was with kernel 2.6.17.13. I upgraded to the latest production 2.6.20 kernel and experienced the same