linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ryan C. Underwood" <nemesis-lists@icequake.net>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Several unhappy btrfs's after RAID meltdown
Date: Tue, 7 Feb 2012 08:04:31 -0600	[thread overview]
Message-ID: <20120207140431.GB5639@localhost.localdomain> (raw)
In-Reply-To: <pan.2012.02.07.09.53.58@cox.net>


> > Unfortunately, I am going to have to give up on btrfs if it
> > is really so fragile.
> 
> However, complaining about the fragility of a still in development
> and 
> marked experimental filesystem would seem disingenuous at best.  
[snip paragraphs of tut-tutting]
> IOW, yes, btrfs is to be considered fragile at this point.

So you re-stated my position.  I gave btrfs a chance but it is still
apparently far more fragile than ext4 when corruption is introduced --
although btrfs is the filesystem of the two which is specifically
designed to provide internal fault tolerance and resilience.  Is there
a fine line between "user feedback" and "disingenuous complaining"
that I am not aware of?

The data in question is not that important, though I would like to
have it back considering it should mostly still be there as on the
ext4 volumes.  40MB of bad sectors on one 2TB disk in a 6TB volume
does not seem like a lot.  Even if the whole beginning of the volume
was wiped out surely there is the equivalent of backup superblocks?  I
can hack if I could just get a clue where to start.

-- 
Ryan C. Underwood, <nemesis@icequake.net>

  reply	other threads:[~2012-02-07 14:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 18:41 Several unhappy btrfs's after RAID meltdown Ryan C. Underwood
2012-02-07  3:39 ` Ryan C. Underwood
2012-02-07  4:17   ` Liu Bo
2012-02-07 15:03     ` Ryan C. Underwood
2012-02-07  9:53   ` Duncan
2012-02-07 14:04     ` Ryan C. Underwood [this message]
2012-02-07 14:36       ` Mitch Harder
2012-02-07 15:42         ` Ryan C. Underwood
2012-02-07 17:46           ` Ryan C. Underwood
2012-02-07 17:49             ` Ryan C. Underwood
2012-02-12 16:31               ` Ryan C. Underwood
2012-02-13 13:48                 ` David Sterba
2012-06-01 14:38                 ` Ryan C. Underwood
2012-11-15 16:00                   ` Ryan C. Underwood
2012-11-16  8:39                     ` Michael Kjörling
2012-02-08  6:32     ` Chris Samuel

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=20120207140431.GB5639@localhost.localdomain \
    --to=nemesis-lists@icequake.net \
    --cc=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nemesis@icequake.net \
    /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).