public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Eric Anopolsky <erpo41@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: parity data
Date: Mon, 08 Sep 2008 10:47:51 -0400	[thread overview]
Message-ID: <1220885271.8537.31.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1220766185.20018.7.camel@telesto>

On Sat, 2008-09-06 at 23:43 -0600, Eric Anopolsky wrote:
> Hi,
> 
> A couple of questions.
> 
> 1. Does btrfs currently have anything like raid 5 or 6?
> 

Not yet, it might one day.

> 2. One guy on my LUG's mailing list is really excited about the
> potential for setting redundancy on a per-file basis.
> I.e. /home/eric/criticalfile gets mirrored across all of the drives in
> the filesystem but /home/eric/temporaryfile gets striped. I'm skeptical.
> Is it a good idea to allow people/programs to do this?

In general, yes.  Some files or directories are crucial, and some (swap
for example) don't need to survive a crash.

But, I think the flexibility should go a little further.  The goal is to
be able to define drive groups and tie files or directory trees to the
drive groups.  That way you can say these files go to the fastest drives
and these files go to some other drive type, etc etc.

-chris



  reply	other threads:[~2008-09-08 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07  5:43 parity data Eric Anopolsky
2008-09-08 14:47 ` Chris Mason [this message]
2008-09-09  0:46   ` Eric Anopolsky
2008-09-09 10:43     ` Chris Mason
2008-09-09 14:07       ` Paul P Komkoff Jr
2008-09-10  1:32       ` Eric Anopolsky
2008-09-10 12:59         ` Chris Mason

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=1220885271.8537.31.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=erpo41@gmail.com \
    --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