From: Hugo Mills <hugo@carfax.org.uk>
To: Peter Chant <pete@petezilla.co.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Hardware failure or btrfs issue?
Date: Tue, 2 Jul 2013 08:29:15 +0100 [thread overview]
Message-ID: <20130702072915.GA8170@carfax.org.uk> (raw)
In-Reply-To: <51D2091E.9010800@petezilla.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
On Mon, Jul 01, 2013 at 11:56:30PM +0100, Peter Chant wrote:
> Sirs,
>
> my recently slowing file system is now going read only after trying
> a defrag or other operation. I'm wondering whether this is the
> result of a hardware failure or a btrfs or some other issue. Output
> of dmesg:
[snip]
> [ 127.862825] btrfs: corrupt leaf, bad key order:
> block=2837196627968,root=1, slot=121
[snip]
This is usually an indication that you have bad hardware -- I'd
suggest testing RAM, PSU, CPU in that order. I'm not sure what, if
anything, can be done to fix the error on the disk right now.
> Not that I've done anything other than a cursory check but it looks
> like the read only data is fine.
Might be a good idea to use that to refresh your backups, just in
case my prediction about the fixability is correct.
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
--- "How deep will this sub go?" "Oh, she'll go all the way to ---
the bottom if we don't stop her."
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-07-02 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 22:56 Hardware failure or btrfs issue? Peter Chant
2013-07-02 7:29 ` Hugo Mills [this message]
2013-07-02 17:36 ` Peter Chant
2013-07-02 17:48 ` Hugo Mills
2013-07-02 21:37 ` Peter Chant
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=20130702072915.GA8170@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=pete@petezilla.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).