On 17/05/2011 20:00, Roman Mamedov wrote:
On Tue, 17 May 2011 22:43:48 +0400
Jason Tinker<jsntinker@xxxxxxxxx> wrote:
Do you have RAID5 over RAID0's or an ordinary RAID5? On my box
ordinary RAID5 works perfectly too.
Yes, I ran RAID5 of 4x2TB+(1+1TB RAID0)+(1.5+0.5TB RAID0), recently changed to
RAID6 though, also replaced one of the RAID0s with another 2TB drive.
If your configuration is also RAID5 over RAID0 and it works fine on
2.6.38 then I'll just wait for next ubuntu lts...
I am not saying you should just give up. The logs you posted seem like
they can be very helpful in tracking this down. But if it is indeed a kernel
issue, how do you fix or even debug it it without replacing/compiling a new
kernel, which is exactly what you do not want to do. And if you're already
replacing a kernel, why not try a 2.6.38 right away, to check if your issue is
already solved in there (after all 2.6.32 vs 2.6.38 are eons apart BOTH
mdadm-wise and ext4-wise).
I've said it before and no doubt I'll say it again, but the RHEL kernels
are often a lot closer to the most recent than their version numbers
suggest. It's a little more difficult to tell with EL6, because Red Hat
don't ship vanilla+patches sources any more, but their .32 series
includes lots of backported fixes from .38 etc.
Jason, it's probably worth testing with vanilla .38 to see if that does
fix your problem, then post to Red Hat bugzilla saying so, especially as
it looks to me like the configuration you're trying to use ought to be a
supported one - then a future RHEL .32 might well include the fix.
Cheers,
John.
(Not a spokesman for Red Hat, nor anyone else other than myself, and
sometimes not even that ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
