From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: Virtual Device Support ("N-way mirror code")
Date: Tue, 21 May 2013 13:19:31 +0100 [thread overview]
Message-ID: <knfoof$u08$1@ger.gmane.org> (raw)
In-Reply-To: <pan$9855$81c2d2df$c9aa1ca3$2451cc46@cox.net>
Duncan,
Thanks for quiet a historical summary.
Yep, ReiserFS has stood the test of time very well and I'm still using
and abusing it still on various servers all the way from something like
a decade ago!
More recently I've been putting newer systems on ext4 mainly to take
advantage of extents for large files on all disk types, and also
deferred allocation to hopefully reduce wear on SSDs.
Meanwhile, I've seen no need to change the ReiserFS on the existing
systems, even for the multi-Terabyte backups. The near unlimited file
linking is beautiful for creating in effect incremental backups spanning
years!
All on raid1 or raid5, and all remarkably robust.
Enough waffle! :-)
On 21/05/13 04:59, Duncan wrote:
> And hopefully, now that btrfs raid5/6 is in, in a few cycles the N-way
> mirrored code will make it as well
I too am waiting for the "N-way mirrored code" for example to have 3
copies of data/metadata across 4 physical disks.
When might that hit? Or is there a stable patch that can be added into
kernel 3.8.13?
Regards,
Martin
next prev parent reply other threads:[~2013-05-21 12:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 14:03 Virtual Device Support George Mitchell
2013-05-19 11:04 ` Martin
2013-05-19 14:49 ` George Mitchell
2013-05-19 17:18 ` Martin
[not found] ` <CAHGunUke143r3pj0Piv3AtJrJO1x8Bm+qS5Z+sY1G1EobhMG_w@mail.gmail.com>
2013-05-21 14:26 ` George Mitchell
2013-05-19 11:15 ` Roman Mamedov
2013-05-19 18:18 ` Chris Murphy
2013-05-19 18:22 ` Chris Murphy
2013-05-21 1:08 ` Duncan
2013-05-21 2:17 ` George Mitchell
2013-05-21 3:59 ` Duncan
2013-05-21 5:21 ` George Mitchell
2013-05-21 12:19 ` Martin [this message]
2013-05-23 16:08 ` Virtual Device Support ("N-way mirror code") Martin Steigerwald
2013-05-24 1:41 ` George Mitchell
2013-05-25 11:53 ` Martin Steigerwald
2013-05-24 6:13 ` Duncan
2013-05-25 11:56 ` Martin Steigerwald
2013-05-21 3:37 ` Virtual Device Support Chris Murphy
2013-05-21 12:06 ` Martin
2013-05-22 2:23 ` Chris Murphy
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='knfoof$u08$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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).