From: Eric Wolf <19wolf@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>, Eric Wolf <19wolf@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: BTRFS critical (device sda2): corrupt leaf, bad key order: block=293438636032, root=1, slot=11
Date: Thu, 31 Aug 2017 14:50:24 -0400 [thread overview]
Message-ID: <CAJ_hD5A8_dxUr781mndBwj7sTf7Aohw4uFCFQGw1k_QNM=psnQ@mail.gmail.com> (raw)
In-Reply-To: <20170831183302.GB30990@carfax.org.uk>
Also, I know it was caused by bad RAM and that ram has since been removed.
---
Eric Wolf
(201) 316-6098
19wolf@gmail.com
On Thu, Aug 31, 2017 at 2:33 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> On Thu, Aug 31, 2017 at 01:53:58PM -0400, Eric Wolf wrote:
>> I'm having issues with a bad block(?) on my root ssd.
>>
>> dmesg is consistently outputting "BTRFS critical (device sda2):
>> corrupt leaf, bad key order: block=293438636032, root=1, slot=11"
>>
>> "btrfs scrub stat /" outputs "scrub status for b2c9ff7b-[snip]-48a02cc4f508
>> scrub started at Wed Aug 30 11:51:49 2017 and finished after 00:02:55
>> total bytes scrubbed: 53.41GiB with 2 errors
>> error details: verify=2
>> corrected errors: 0, uncorrectable errors: 2, unverified errors: 0"
>>
>> Running "btrfs check --repair /dev/sda2" from a live system stalls
>> after telling me corrupt leaf etc etc then "11 12". CPU usage hits
>> 100% and disk activity remains at 0.
>
> This error is usually attributable to bad hardware. Typically RAM,
> but might also be marginal power regulation (blown capacitor
> somewhere) or a slightly broken CPU.
>
> Can you show us the output of "btrfs-debug-tree -b 293438636032 /dev/sda2"?
>
> Hugo.
>
> --
> Hugo Mills | "You got very nice eyes, Deedee. Never noticed them
> hugo@... carfax.org.uk | before. They real?"
> http://carfax.org.uk/ |
> PGP: E2AB1DE4 | Don Logan, Sexy Beast
prev parent reply other threads:[~2017-08-31 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 17:53 BTRFS critical (device sda2): corrupt leaf, bad key order: block=293438636032, root=1, slot=11 Eric Wolf
2017-08-31 18:33 ` Hugo Mills
2017-08-31 18:44 ` Eric Wolf
2017-08-31 18:59 ` Hugo Mills
2017-08-31 19:21 ` Eric Wolf
2017-08-31 20:11 ` Hugo Mills
2017-09-01 13:38 ` Eric Wolf
2017-09-01 20:29 ` Chris Murphy
2017-09-01 13:42 ` Eric Wolf
2017-08-31 18:50 ` Eric Wolf [this message]
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='CAJ_hD5A8_dxUr781mndBwj7sTf7Aohw4uFCFQGw1k_QNM=psnQ@mail.gmail.com' \
--to=19wolf@gmail.com \
--cc=hugo@carfax.org.uk \
--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).