From: Martin Steigerwald <Martin@lichtvoll.de>
To: Martin <m_btrfs@ml1.co.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Virtual Device Support ("N-way mirror code")
Date: Thu, 23 May 2013 18:08:35 +0200 [thread overview]
Message-ID: <1823670.hMFQUu2mCu@merkaba> (raw)
In-Reply-To: <knfoof$u08$1@ger.gmane.org>
Am Dienstag, 21. Mai 2013, 13:19:31 schrieb Martin:
> 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!
Very interesting. I only used it for a short time and it worked.
But co-workers lost several ReiserFS filesystems completely.
Well, if you search for the terms corrupt and your favorite filesystem, you
will always find hits.
Anyway, I won´t use ReiserFS 3 today for several reasons:
1) It is not yet actively developed anymore, but more in a maintenance. I know
for some that might be a reason to use it, but I think this basically
increases the risk of breakages instead of reducing it. That said, I didn´t
hear of any, and also JFS is in maintenance, but appears to work as well.
2) As to my knowledge a fsck.reiserfs cannot tell the filesystem I check and
possible ReiserFS3 filesystems in virtual machine image files on it appart,
happily mixing them together in a huge big mess.
3) As to my knowledge mount times of large partitions can be quite long with
ReiserFS 3.
That said, I am using BTRFS on my main laptop even for /home now after having
used it on several other machines for more than a year. Despite from that
wierd scrub issue that I "fixed" by redoing the filesystem, rsync backup
appeared t be okay, I am ready to trust my data to BTRFS. Also my backup
harddisks are BTRFS.
I like BTRFS for some reasons, two that immediately come to my mind:
1) It can prove to me that the data is intact. I find this rather valuable.
2) Due to snapshots I know have well snapshots for my backup. And even on SSD
for my /home. I am not yet creating those in an automated way, but well I do
use them.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2013-05-23 16:08 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 ` Virtual Device Support ("N-way mirror code") Martin
2013-05-23 16:08 ` Martin Steigerwald [this message]
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=1823670.hMFQUu2mCu@merkaba \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=m_btrfs@ml1.co.uk \
/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).