On September 28, 2011, Brad Campbell wrote: > On 28/09/11 18:38, Michal Soltys wrote: > > It's hard to find cases, when md driver or mdadm was really at fault for > > something. For the most part the typical route is: [bottom barrel cheap > > desktop ]hardware/[terribly designed sata ]cable issues -> a user > > applying random googled suggestions (with shaking hands) -> really, > > really bad problems. But that's not md's failure. > > This really sums it up succinctly. > > If you watched the cases of disaster that swing past linux-raid, the > ones who always walk away whistling a happy tune are the ones who stop, > think and ask for help. > > The basket cases are more often than not created by people trying stuff > out because they saw it mentioned somewhere else. > > I'd suggest that users of real hardware raid suffer less "problems" > because as they pay a bucketload of money for their raid card, they are > far less likely to cheap out on cables, enclosures, drives and power > supplies. > > Most of the tales of woe here are related to the failures associated > with commodity hardware. The 8TB I lost was entirely due to using a $15 > SATA controller. > I completely agree. The last time I lost my array, it was because I fat fingered a mdadm command. Can't remember exactly what it was now, either a reshape, or a drive replacement. Now I try to be very very careful. -- Thomas Fjellstrom thomas@xxxxxxxxxxxxx -- 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
