On Fri, Jul 3, 2015 at 9:05 AM, Donald Pearson <donaldwhpear...@gmail.com> wrote:
> I did some more digging and found that I had a lot of errors basically > every drive. Ick. Sucks for you but then makes this less of a Btrfs problem because it can really only do so much if more than the number of spares have problems. It does suggest a more aggressive need for the volume to go read only in such cases though, before it gets this corrupt. Multiple disk problems like this though suggest a shared hardware problem like a controller or expander. > So one particularly bad drive + multiple raid56 caveats + all the > other drives behaving a little funny + a guy who didn't read as well > as he should, and I really can't be surprised at the result. > > So I've decided to cash in the pool for some valueable lessons and > move on. Thanks to everybody for your thoughts and help here and on > IRC (a responsive IRC, that's a refereshing difference) and I'll see > what adventures btrfs round 2 brings. Yep! -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
