Re: RAID56 status?

+1 On martedì 24 gennaio 2017 00:31:42 CET, Christoph Anton Mitterer wrote: On Mon, 2017-01-23 at 18:18 -0500, Chris Mason wrote: We've been focusing on the single-drive use cases internally. This year that's changing as we ramp up more users in different places. Performance/stability work

Re: RAID56 status?

On Mon, 2017-01-23 at 18:18 -0500, Chris Mason wrote: > We've been focusing on the single-drive use cases internally.  This > year  > that's changing as we ramp up more users in different places.   > Performance/stability work and raid5/6 are the top of my list right > now. +1 Would be nice to

Re: RAID56 status?

On Mon, Jan 23, 2017 at 06:53:21PM +0100, Christoph Anton Mitterer wrote: Just wondered... is there any larger known RAID56 deployment? I mean something with real-world production systems and ideally many different IO scenarios, failures, pulling disks randomly and perhaps even so many disks

Re: RAID56 status?

Just wondered... is there any larger known RAID56 deployment? I mean something with real-world production systems and ideally many different IO scenarios, failures, pulling disks randomly and perhaps even so many disks that it's also likely to hit something like silent data corruption (on the

Re: RAID56 status?

On Mon, Jan 23, 2017 at 7:57 AM, Brendan Hide wrote: > > raid0 stripes data in 64k chunks (I think this size is tunable) across all > devices, which is generally far faster in terms of throughput in both > writing and reading data. I remember seeing some proposals for

Re: RAID56 status?

Hey, all Long-time lurker/commenter here. Production-ready RAID5/6 and N-way mirroring are the two features I've been anticipating most, so I've commented regularly when this sort of thing pops up. :) I'm only addressing some of the RAID-types queries as Qu already has a handle on the

Re: RAID56 status?

At 01/23/2017 12:42 PM, Zane Zakraisek wrote: Hi Qu, I've seen a good amount of Raid56 patches come in from you on the mailing list. Do these catch a large portion of the Raid56 bugs, or are they only the beginning? :) Hard to say, it can be just tip of a iceberg, or beginning of RAID56

Re: RAID56 status?

At 01/23/2017 08:25 AM, Jan Vales wrote: On 01/22/2017 11:39 PM, Hugo Mills wrote: On Sun, Jan 22, 2017 at 11:35:49PM +0100, Christoph Anton Mitterer wrote: On Sun, 2017-01-22 at 22:22 +0100, Jan Vales wrote: Therefore my question: whats the status of raid5/6 is in btrfs? Is it somehow

Re: RAID56 status?

On 01/22/2017 11:39 PM, Hugo Mills wrote: > On Sun, Jan 22, 2017 at 11:35:49PM +0100, Christoph Anton Mitterer wrote: >> On Sun, 2017-01-22 at 22:22 +0100, Jan Vales wrote: >>> Therefore my question: whats the status of raid5/6 is in btrfs? >>> Is it somehow "production"-ready by now? >> AFAIK,

Re: RAID56 status?

Hugo Mills wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Jan 22, 2017 at 11:35:49PM +0100, Christoph Anton Mitterer wrote: On Sun, 2017-01-22 at 22:22 +0100, Jan Vales wrote: Therefore my question: whats the status of raid5/6 is in btrfs? Is it somehow "production"-ready by

Re: RAID56 status?

On Sun, 2017-01-22 at 22:39 +, Hugo Mills wrote: >    It's still all valid. Nothing's changed. > >    How would you like it to be updated? "Nope, still broken"? The kernel version mentioned there is 4.7... so noone (at least endusers) really knows whether it's just no longer maintainer or

Re: RAID56 status?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Jan 22, 2017 at 11:35:49PM +0100, Christoph Anton Mitterer wrote: > On Sun, 2017-01-22 at 22:22 +0100, Jan Vales wrote: > > Therefore my question: whats the status of raid5/6 is in btrfs? > > Is it somehow "production"-ready by now? > AFAIK,

Re: RAID56 status?

On Sun, 2017-01-22 at 22:22 +0100, Jan Vales wrote: > Therefore my question: whats the status of raid5/6 is in btrfs? > Is it somehow "production"-ready by now? AFAIK, what's on the - apparently already no longer updated -  https://btrfs.wiki.kernel.org/index.php/Status still applies, and RAID56