On Wed, Mar 9, 2016 at 9:06 PM, Duncan <1i5t5.duncan@xxxxxxx> wrote: > Tho hopefully all the really tough problems they would have hit with N- > way-mirroring were hit and resolved with raid56, and N-way-mirroring will > thus be relatively simple, so hopefully it's less than the four years > it's taking raid56. But I don't expect to see it for another year or > two, and don't expect to be actually use it as intended (as a more > failure resistant raid1) for some time after that as the bugs get worked > out, so realistically, 2-3 years. > > If multi-device scheduling optimization is done in say 6 months after > that... that means we're looking at 2.5-3.5 years, perhaps longer, for > it. So it's a known issue, yes, and on the roadmap, yes, but don't > expect to see anything in the near (-2-year) future, more like > intermediate (3-5) year future. In all honesty I don't seriously expect > it to be long-term future, beyond 5 years, but it's possible. Meh, encryption RFC patches arrived 8 days ago and I wasn't expecting that to happen for a couple years. So I think our expectations have almost no bearing on feature or fix arrival. For all we know n-way could appear in 4.6. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
