From: "Niels de Carpentier" <niels@decarpentier.com>
To: "cwillu" <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Re: Two way mirror in BRTFS
Date: Fri, 30 Dec 2011 16:57:34 +0100 [thread overview]
Message-ID: <763e6c305540e062472df4b20854a62e.squirrel@webmail.decarpentier.com> (raw)
In-Reply-To: <CAE5mzviVPjHwem85ogbHEn6YhzmpqXGh25UjtbTTvD6gMnhnAw@mail.gmail.com>
>> For btrfs bugs are still fixed on a daily basis, and some reports of
>> people with corrupted and unrecoverable filesystems.
>
> I don't know that there's been any actual unrecoverable filesystems
> recently; unmountable is by far the more common issue, and given that
> most sane people aren't putting their only copy of important
> information on btrfs filesystems, their preference tends to be towards
> wiping and starting over rather than spending a week to recover the
> information by hand (the recovery tools that exist are the results of
> the few who chose the other option).
>
> I think "... people with corrupted and not easily recoverable" would
> be a better summary.
Yes, you are right, in most cases most/all of the data is recoverable.
There was this case:
http://article.gmane.org/gmane.comp.file-systems.btrfs/14755
But that one might be recoverable as well.
I'm sure btrfs will become the main linux filesystem of the future, it's
just not there yet. The mythical btrfsck might change this. But neither
btrfs or zfs on linux should currently be used for important production
systems.
Niels
next prev parent reply other threads:[~2011-12-30 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 11:41 Who way mirror in BRTFS Jaromir Zdrazil
2011-12-30 12:32 ` Two " Jaromir Zdrazil
2011-12-30 13:27 ` Fajar A. Nugraha
2011-12-30 13:59 ` Jaromir Zdrazil
2011-12-30 14:33 ` Fajar A. Nugraha
2011-12-30 15:27 ` Jaromir Zdrazil
2011-12-30 16:01 ` Niels de Carpentier
2011-12-30 16:45 ` Fajar A. Nugraha
2011-12-30 15:08 ` Niels de Carpentier
2011-12-30 15:31 ` cwillu
2011-12-30 15:57 ` Niels de Carpentier [this message]
2011-12-31 0:19 ` Jaromir Zdrazil
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=763e6c305540e062472df4b20854a62e.squirrel@webmail.decarpentier.com \
--to=niels@decarpentier.com \
--cc=cwillu@cwillu.com \
--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).