From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT
Date: Sat, 4 Jan 2014 20:08:54 +0000 (UTC) [thread overview]
Message-ID: <pan$a3e91$3573a989$f0de8522$780fffaf@cox.net> (raw)
In-Reply-To: 1388847120.23513.21.camel@ret.masoncoding.com
Chris Mason posted on Sat, 04 Jan 2014 14:51:23 +0000 as excerpted:
> It'll pick the latest generation number and use that one as the one true
> source. For the others you'll get crc errors which make it fall back to
> the latest one. If the two have exactly the same generation number,
> we'll have a hard time picking the best one.
>
> Ilya has a series of changes from this year's GSOC that we need to clean
> up and integrate. It detects offline devices and brings them up to date
> automatically.
>
> He targeted the pull-one-drive use case explicitly.
Thanks for the explanation and bits to look forward to.
I'll be looking forward to seeing that GSOC stuff then, as having
dropouts and re-adds auto-handled would be a sweet feature to add to the
raid featureset, improving things from a sysadmin's prepared-to-deal-with-
recovery perspective quite a bit. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-01-04 20:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 22:28 btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT Jim Salter
2014-01-03 22:42 ` Emil Karlson
2014-01-03 22:43 ` Joshua Schüler
2014-01-03 22:56 ` Jim Salter
2014-01-03 23:04 ` Hugo Mills
2014-01-03 23:04 ` Joshua Schüler
2014-01-03 23:13 ` Jim Salter
2014-01-03 23:18 ` Hugo Mills
2014-01-03 23:25 ` Jim Salter
2014-01-03 23:32 ` Chris Murphy
2014-01-03 23:22 ` Chris Murphy
2014-01-04 6:10 ` Duncan
2014-01-04 11:20 ` Chris Samuel
2014-01-04 13:03 ` Duncan
2014-01-04 14:51 ` Chris Mason
2014-01-04 15:23 ` Goffredo Baroncelli
2014-01-04 20:08 ` Duncan [this message]
2014-01-04 21:22 ` Jim Salter
2014-01-05 11:01 ` Duncan
2014-01-03 23:19 ` Chris Murphy
[not found] ` <CAOjFWZ7zC3=4oH6=SBZA+PhZMrSK1KjxoRN6L2vqd=GTBKKTQA@mail.gmail.com>
2014-01-03 23:42 ` Jim Salter
2014-01-03 23:45 ` Jim Salter
2014-01-04 0:27 ` Chris Murphy
2014-01-04 2:59 ` Jim Salter
2014-01-04 5:57 ` Dave
2014-01-04 11:28 ` Chris Samuel
2014-01-04 14:56 ` Chris Mason
2014-01-05 9:20 ` Chris Samuel
2014-01-05 11:16 ` Duncan
2014-01-04 19:18 ` Chris Murphy
2014-01-04 21:16 ` Jim Salter
2014-01-05 20:25 ` Chris Murphy
2014-01-06 10:20 ` Chris Samuel
2014-01-06 18:30 ` Chris Murphy
2014-01-06 19:25 ` Jim Salter
2014-01-06 22:05 ` Chris Murphy
2014-01-06 22:24 ` Jim Salter
2014-01-07 5:43 ` Chris Samuel
2014-01-06 19:31 ` correct way to rollback a root filesystem? Jim Salter
2014-01-07 11:55 ` Sander
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='pan$a3e91$3573a989$f0de8522$780fffaf@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 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.