On Thu, Nov 17, 2016 at 12:20 PM, Austin S. Hemmelgarn <ahferro...@gmail.com> wrote: > On 2016-11-17 15:05, Chris Murphy wrote: >> >> I think the wiki should be updated to reflect that raid1 and raid10 >> are mostly OK. I think it's grossly misleading to consider either as >> green/OK when a single degraded read write mount creates single chunks >> that will then prevent a subsequent degraded read write mount. And >> also the lack of various notifications of device faultiness I think >> make it less than OK also. It's not in the "do not use" category but >> it should be in the middle ground status so users can make informed >> decisions. >> > It's worth pointing out also regarding this: > * This is handled sanely in recent kernels (the check got changed from > per-fs to per-chunk, so you still have a usable FS if all the single chunks > are only on devices you still have).
The status page should reflect the version with sane behavior, relative to the versions with not sane behavior. Otherwise people hit it unexpectedly despite the status page. But still, the multiple device stuff really is not "OK" until there's some kind of faulty device concept and also notification for state changes from normal to faulty, faulty to normal, or even failed if that's reliably distinguishable from faulty. > As far as the failed device handling issues, those are a problem with BTRFS > in general, not just raid1 and raid10, so I wouldn't count those against > raid1 and raid10. Sure but raid56 are already flagged as not ready for prime time. -- 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
