From: Chris Mason <chris.mason@fusionio.com>
To: Russell Coker <russell@coker.com.au>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Debian 3.7.1 BTRFS crash
Date: Wed, 13 Mar 2013 15:19:18 -0400 [thread overview]
Message-ID: <20130313191918.GF15014@shiny.masoncoding.com> (raw)
In-Reply-To: <201303140103.53907.russell@coker.com.au>
On Wed, Mar 13, 2013 at 08:03:53AM -0600, Russell Coker wrote:
> On Thu, 14 Mar 2013, Eric Sandeen <sandeen@redhat.com> wrote:
> > > It seems the SSD has bad blocks now, BTRFS seems to abuse SSD disks, I
> > > burnt 1 SSD disk and 2 USB flash drive since I'm using BTRFS, in about
> > > 2 months for each. ddrescue'ing the SSD would probably give better
> > > chances of recovery and give BTRFS/btrfsck a chance to write correctly
> > > to the newly copied image.
> >
> > On what do you base that theory? I suppose it could be, but nothing
> > in the logs necessarily suggests that. The "IO failure" is because
> > the fs shut down, went readonly, and subsequent IOs got -EIO,
> > I think.
>
> I've just used nc to transfer the filesystem to another system, there were no
> read errors so I don't think that a SSD hardware failure is the problem here.
>
> I'm now getting similar problems running a 3.8 kernel with the filesystem on a
> loopback device. I'll provide more information soon.
Bad key ordering is pretty rare, and it usually means memory
corruptions. Are you reproducing this on the same machine or a
different one?
-chris
next prev parent reply other threads:[~2013-03-13 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 1:38 Debian 3.7.1 BTRFS crash Russell Coker
2013-03-13 1:56 ` Harald Glatt
2013-03-13 2:03 ` Eric Sandeen
2013-03-13 5:07 ` Jérôme Poulin
2013-03-13 10:56 ` Bart Noordervliet
2013-03-13 11:31 ` Swâmi Petaramesh
2013-03-14 19:04 ` Norbert Scheibner
2013-03-14 23:17 ` Martin Steigerwald
2013-03-13 13:47 ` Eric Sandeen
2013-03-13 14:03 ` Russell Coker
2013-03-13 19:19 ` Chris Mason [this message]
2013-03-14 6:36 ` Russell Coker
2013-03-14 13:04 ` Chris Mason
2013-03-14 9:48 ` Martin Steigerwald
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=20130313191918.GF15014@shiny.masoncoding.com \
--to=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.