linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: David Pottage <david@chrestomanci.org>,
	Vimal A R <arvimal@yahoo.in>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Ideas for a feature implementation
Date: Wed, 13 Aug 2014 14:05:14 +0300	[thread overview]
Message-ID: <53EB466A.40605@gmail.com> (raw)
In-Reply-To: <53EB4581.8050104@chrestomanci.org>

On 13/8/2014 2:01 μμ, David Pottage wrote:
>
> On 12/08/14 12:00, Konstantinos Skarlatos wrote:
>> Maybe help with Andrea Mazzoleni's New RAID library supporting up to 
>> six parities? It seems to be a great feature for btrfs.
>>
>> https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg31735.html
>
> That would be very cool, but at present vanila RAID 5 or 6 does not 
> work properly, so I think getting that fully working would be a better 
> idea. (Unless it would make more sense to merge the whole lot into one 
> bit of work where RAID 5 or 6 are just a special case of arbitrary 
> parity level support).
>
> At present, you can write RAID 5 or 6 data, but if anything goes 
> wrong, btrfs cannot use the parity information to help you get your 
> data back, so in general you are better off with RAID 1 or 10. Also, I 
> don't think I/O done in parallel so you get no speed advantage from 
> having multiple discs either.
>
Yeah, thats one of the features I am waiting to get finished, because I 
already have 5 multi disk systems that i would prefer to migrate to 
RAID5/6 from RAID1/JBOD that they are now.

I dont know what is the best sequencing, I just think that these are 
great patches/features and its a pity for them to languish.


-- 
Konstantinos Skarlatos


  reply	other threads:[~2014-08-13 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 19:21 Ideas for a feature implementation Vimal A R
2014-08-11  2:53 ` Austin S Hemmelgarn
2014-08-11 20:27   ` Chris Murphy
2014-08-12  2:27     ` Austin S Hemmelgarn
2014-08-12  3:04       ` Chris Murphy
2014-08-12 15:52   ` David Pottage
2014-08-12 17:34     ` Austin S Hemmelgarn
2014-08-13 12:26     ` Brendan Hide
2014-08-12 16:38   ` Erkki Seppala
2014-08-12 11:00 ` Konstantinos Skarlatos
2014-08-13 11:01   ` David Pottage
2014-08-13 11:05     ` Konstantinos Skarlatos [this message]
2014-08-17 21:17     ` Chris Murphy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53EB466A.40605@gmail.com \
    --to=k.skarlatos@gmail.com \
    --cc=arvimal@yahoo.in \
    --cc=david@chrestomanci.org \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).