From: "Jason D. Michaelson" <jasondmichaelson@gmail.com>
To: "'Chris Murphy'" <lists@colorremedies.com>
Cc: "'Btrfs BTRFS'" <linux-btrfs@vger.kernel.org>
Subject: RE: raid6 file system in a bad state
Date: Mon, 17 Oct 2016 13:52:45 -0500 [thread overview]
Message-ID: <065201d228a7$a6e683a0$f4b38ae0$@com> (raw)
In-Reply-To: <CAJCQCtQAomLb9ysym5q_rqjFW8uJCpTM0Y-wUSjywte-AQkSMg@mail.gmail.com>
I've been following that thread. It's been my fear.
I'm in the process of doing a restore of what I can get off of it so that i can re-create the file system with raid1 which, if i'm reading that thread correctly doesn't suffer at all from the rmw problems extant in the raid5/6 code at the moment.
Again, thanks for your help.
> -----Original Message-----
> From: chris@colorremedies.com [mailto:chris@colorremedies.com] On
> Behalf Of Chris Murphy
> Sent: Friday, October 14, 2016 4:55 PM
> To: Chris Murphy
> Cc: Jason D. Michaelson; Btrfs BTRFS
> Subject: Re: raid6 file system in a bad state
>
> This may be relevant and is pretty terrible.
>
> http://www.spinics.net/lists/linux-btrfs/msg59741.html
>
>
> Chris Murphy
prev parent reply other threads:[~2016-10-17 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 16:04 raid6 file system in a bad state Jason D. Michaelson
2016-10-10 20:59 ` Chris Murphy
[not found] ` <5ce201d22364$96702780$c3507680$@com>
2016-10-11 4:23 ` Chris Murphy
2016-10-11 15:52 ` Jason D. Michaelson
2016-10-11 16:06 ` Chris Murphy
2016-10-11 16:10 ` Jason D. Michaelson
2016-10-11 17:41 ` Chris Murphy
[not found] ` <5e8701d223f1$c7ea0960$57be1c20$@com>
2016-10-11 20:38 ` Chris Murphy
2016-10-12 17:59 ` Jason D. Michaelson
2016-10-12 19:36 ` Chris Murphy
2016-10-14 21:54 ` Chris Murphy
2016-10-17 18:52 ` Jason D. Michaelson [this message]
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='065201d228a7$a6e683a0$f4b38ae0$@com' \
--to=jasondmichaelson@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.