From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Robert Krig <robert.krig@render-wahnsinn.de>,
linux-btrfs@vger.kernel.org
Subject: Re: Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block"
Date: Mon, 3 Apr 2017 16:09:22 +0200 [thread overview]
Message-ID: <1d84e84a-7fce-7d21-25c8-107453a75db6@mendix.com> (raw)
In-Reply-To: <40314a4f-612b-ec45-36ba-75da52ddc9f9@render-wahnsinn.de>
On 04/03/2017 03:50 PM, Robert Krig wrote:
>
>
> On 03.04.2017 12:11, Robert Krig wrote:
>> Hi guys, I seem to have run into a spot of trouble with my btrfs partition.
>>
>> I've got 4 x 8TB in a RAID1 BTRFS configuration.
>>
>> I'm running Debian Jessie 64 Bit, 4.9.0-0.bpo.2-amd64 kernel. Btrfs
>> progs version v4.7.3
>>
>> Server has 8GB of Ram.
>>
>>
>> I was running duperemove using a hashfile, which seemed to have run out
>> space and aborted. Then I tried a balance operation, with -dusage
>> progressively set to 0 1 5 15 30 50, which then aborted, I presume that
>> this caused the fs to mount readonly. I only noticed it somewhat later.
>>
>> I've since rebooted, and I can mount the filesystem OK, but after some
>> time (I presume caused by reads or writes) it once again switches to
>> readonly.
>>
>> I tried unmounting/remounting again and running a scrub, but the scrub
>> aborts after some time.
>>
>>
>
>
> I've compiled the newest btrfs-tools version 4.10.2
>
> This is what I get when running a btrfsck -p /dev/sda
>
> hecking filesystem on
> /dev/sda
>
> UUID:
> 8c4f8e26-3442-463f-ad8a-668dfef02593
>
> incorrect offsets 8590
> 1258314415
>
> bad block
> 38666170826752
>
>
>
> ERROR: errors found in extent allocation tree or chunk
> allocation
> Speicherzugriffsfehler
>
> For the non-german speakers: Speicherzugriffsfehler = Memory Access Error
>
> Dmesg shows this:
>
> Apr 03 15:47:05 atlas kernel: btrfs[9140]: segfault at 9476b99e ip
> 000000000044c459 sp 00007fff556b4b10 error 4 in
> btrfs[400000+9d000]
That's probably because the tool does not verify if the numbers in the
fields make sense before using them.
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-04-03 14:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 10:11 Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block" Robert Krig
2017-04-03 13:50 ` Robert Krig
2017-04-03 14:09 ` Hans van Kranenburg [this message]
2017-04-03 14:08 ` Hans van Kranenburg
2017-04-03 14:20 ` Robert Krig
2017-04-03 14:25 ` Robert Krig
2017-04-04 4:02 ` Robert Krig
2017-04-04 13:29 ` Brian B
2017-04-04 13:48 ` Hugo Mills
2017-04-04 13:52 ` Austin S. Hemmelgarn
2017-04-04 16:52 ` Chris Murphy
2017-04-04 16:55 ` Chris Murphy
2017-04-05 6:07 ` Robert Krig
2017-04-03 14:44 ` Hans van Kranenburg
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=1d84e84a-7fce-7d21-25c8-107453a75db6@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=robert.krig@render-wahnsinn.de \
/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).