From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: I need to P. are we almost there yet?
Date: Sun, 4 Jan 2015 03:22:53 +0000 (UTC) [thread overview]
Message-ID: <pan$1d2cd$b8c74fee$d1b247b8$e5de75c@cox.net> (raw)
In-Reply-To: CAAe=sHXzrAoFr9wPUk49F5kV6knpWM7PtdxfNWBRXvpU0b+PgQ@mail.gmail.com
sys.syphus posted on Sat, 03 Jan 2015 12:55:27 -0600 as excerpted:
>> But btrfs raid56 mode should be complete with kernel 3.19 and
>> presumably btrfs-progs 3.19 tho I'd give it a kernel or two to mature
>> to be sure. N-way-mirroring (my particular hotly awaited feature) is
>> next up, but given the time raid56 took, I don't think anybody's
>> predicting when it'll be actually in-tree and ready for use.
>>
>>
> is that the feature where you say i want x copies of this file and y
> copies of this other file? e.g. raid at the file level, with the ability
> to adjust redundancy by file?
Per-file isn't available yet, tho at least per-subvolume is roadmapped,
and now that we have the properties framework working via xattr for files
as well, at least in theory, there is AFAIK no reason to limit it to per-
subvolume, as per-file should be about as easy once the code that
currently limits it to per-filesystem is rewritten.
But actually fully working per-filesystem raid56 is enough for a lot of
people, and actually working per-filesystem N-way-mirroring is what I'm
after, since I already setup multiple filesystems in ordered to keep my
data eggs from all being in the same filesystem basket.
--
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:[~2015-01-04 3:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 18:56 I need to P. are we almost there yet? sys.syphus
2014-12-29 19:00 ` sys.syphus
2014-12-29 19:04 ` Hugo Mills
2014-12-29 20:25 ` sys.syphus
2014-12-29 21:50 ` Hugo Mills
2014-12-29 21:16 ` Chris Murphy
2014-12-30 0:20 ` ashford
[not found] ` <CALBWd85UsSih24RhwpmDeMjuMWCKj9dGeuZes5POj6qEFkiz2w@mail.gmail.com>
2014-12-30 17:09 ` Fwd: " Jose Manuel Perez Bethencourt
2014-12-30 21:44 ` Phillip Susi
2014-12-30 23:17 ` ashford
2014-12-31 2:45 ` Phillip Susi
2014-12-31 17:27 ` ashford
2014-12-31 23:38 ` Phillip Susi
2015-01-01 1:26 ` Chris Samuel
2015-01-01 20:12 ` Roger Binns
2015-01-02 3:47 ` Duncan
2015-01-02 13:42 ` Austin S Hemmelgarn
2015-01-02 17:45 ` Brendan Hide
2015-01-02 19:41 ` Austin S Hemmelgarn
2014-12-29 21:13 ` Chris Murphy
2015-01-03 11:34 ` Bob Marley
2015-01-03 13:11 ` Duncan
2015-01-03 18:53 ` Bob Marley
2015-01-03 19:03 ` sys.syphus
2015-01-03 18:55 ` sys.syphus
2015-01-04 3:22 ` Duncan [this message]
2015-01-04 3:54 ` Hugo Mills
2015-01-03 21:58 ` Roman Mamedov
2015-01-04 3:24 ` Duncan
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$1d2cd$b8c74fee$d1b247b8$e5de75c@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 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).