Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: Gordon Manning <jgordon.manning@gmail.com>
Cc: Chris Mason <clmason@fusionio.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: experimental raid5/6 code in git
Date: Mon, 11 Feb 2013 10:13:51 -0500	[thread overview]
Message-ID: <20130211151351.GA10679@shiny> (raw)
In-Reply-To: <CAM_ZMPCAcKtOH4UapR8HbSN6Woi7Lh7mqy+e14TDY+8tM386iQ@mail.gmail.com>

On Sun, Feb 10, 2013 at 03:35:05PM -0700, Gordon Manning wrote:
>    Hi,
>    Is the BTRFS raid code susceptible to RAID-5 write holes? �I think with
>    the original plan, the problem was avoided by always giving full stripe
>    writes to the raid layers. �Does the current plan deal with the hole in a
>    different manner?

The current code in my git tree does not deal with the raid-5 write
hole.  That's the part I'm finishing off now.

-chris

  parent reply	other threads:[~2013-02-11 15:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-02 16:02 experimental raid5/6 code in git Chris Mason
2013-02-03 17:33 ` Hendrik Friedel
2013-02-04 21:42 ` H. Peter Anvin
2013-02-05  1:23   ` Chris Mason
2013-02-05  2:26     ` H. Peter Anvin
2013-02-05  2:59       ` Gareth Pye
2013-02-05  5:29         ` Chester
2013-02-05  6:10           ` Gareth Pye
2013-02-05 14:22 ` Tomasz Torcz
2013-02-05 18:32   ` Chris Mason
     [not found] ` <CAM_ZMPCAcKtOH4UapR8HbSN6Woi7Lh7mqy+e14TDY+8tM386iQ@mail.gmail.com>
2013-02-11 15:13   ` Chris Mason [this message]
2013-02-12 15:16 ` Kaspar Schleiser
2013-02-12 15:30   ` 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=20130211151351.GA10679@shiny \
    --to=chris.mason@fusionio.com \
    --cc=clmason@fusionio.com \
    --cc=jgordon.manning@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