Messages in this thread | | | From | Neil Brown <> | Date | Thu, 19 Jan 2006 11:13:23 +1100 | Subject | Re: FYI: RAID5 unusably unstable through 2.6.14 |
| |
On Tuesday January 17, cynbe@muq.org wrote: > > Just in case the RAID5 maintainers aren't aware of it:
Others have replied, but just so that you know that the "RAID5 maintainer" is listening, I will too.
You refer to "current" implementation and then talk about " a variety of 2.4 and 2.6" releases.... Not all of them are 'current'.
The 'current' raid5 (in 2.6.15) is much more resilient against read errors than earlier versions.
If you are having transient errors that really are very transient, then the device driver should be retrying more I expect.
If you are having random connectivity error causing transient errors, then your hardware is too unreliable for raid5 to code with.
As has been said, there *is* a supported way to regain a raid5 after connectivity problems - mdadm --assemble --force.
The best way to help with the improvement of md/raid5 is to give precise details of situations where md/raid5 doesn't live up to your expectations. Without precise details it is hard to make progress.
Thankyou for your interest.
NeilBrown - 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/
| |