From: Hugo Mills <hugo@carfax.org.uk>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs crash with a corrupted(?) filesystem
Date: Tue, 4 Feb 2014 16:32:35 +0000 [thread overview]
Message-ID: <20140204163235.GC6490@carfax.org.uk> (raw)
In-Reply-To: <20140204222310.65c4a468@natsu>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
On Tue, Feb 04, 2014 at 10:23:10PM +0600, Roman Mamedov wrote:
> Hello,
>
> My server had a period of instability (PSU-related issues), some lockups,
> some strange crashes, and some files became corrupted, and perhaps parts of
> a filesystem too. One BTRFS partition now fails with the following errors.
>
> On an attempt to make a snapshot:
>
> [ 48.035664] btrfs: corrupt leaf, bad key order: block=193529446400,root=1, slot=9
[snip]
Bad key order is pretty much always down to hardware corrupting
data at some point -- which would go well with your list of hardware
problems above.
> Currently I have it mounted read-only, and all data seems to be accessible.
> Short of copying everything away and recreating the FS, how can I bring it to
> a working order. Is btrfsck a good option here?
The first investigation to do would be to look at the block in
question and see if it's got an obvious problem with it. If you post
the output of "btrfs-debug-tree -b 193529446400 /dev/whatever", we can
take a look at the indexing.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- You're never alone with a rubber duck... ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-02-04 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 16:23 btrfs crash with a corrupted(?) filesystem Roman Mamedov
2014-02-04 16:32 ` Hugo Mills [this message]
2014-02-04 16:35 ` Roman Mamedov
2014-02-04 16:40 ` Hugo Mills
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=20140204163235.GC6490@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.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).