From: Andreas Reis <andreas.reis@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes
Date: Tue, 22 Apr 2014 20:16:13 +0200 [thread overview]
Message-ID: <5356B1ED.8060608@gmail.com> (raw)
In-Reply-To: <53556DCC.3000108@gmail.com>
Same failure with btrfs-progs from integration-20140421 (apart from the
line number 1156).
Can I get a bit of input on this? Is it safe to just ignore the error
for now (as I'm doing atm), ie. remount as rw to skip the orphan cleanup?
Might it even be safe to call btrfs check --repair on the partition? I'm
not keen on that failing mid-process at the same assertion and thus
breaking it over a bunch of minor files, just like it happened with my
previous btrfs partitions.
On 21.04.2014 21:13, Andreas Reis wrote:
> Alright, turns out the partition does actually mount on 3.15-rc2 (error
> messages remain, of course).
>
> But systemd will fail to continue booting as /bin/mount returns "exit
> status 32" and / thus ends as ro, yet can be manually remounted as rw.
>
> Another error message I've spotted with 3.15 is
>
> BTRFS error (device sdc5): error loading props for ino 1810424 (root
> 257): -5
>
> I've now tried to mount with -o recovery and clear_cache, no effect.
next prev parent reply other threads:[~2014-04-22 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 16:16 Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes Andreas Reis
2014-04-21 19:13 ` Andreas Reis
2014-04-21 23:44 ` Duncan
2014-04-22 18:16 ` Andreas Reis [this message]
2014-04-23 2:55 ` Duncan
2014-04-25 2:04 ` Bug: Andreas Reis
2014-04-25 2:43 ` Bug: Partition borked Andreas Reis
2014-04-25 3:03 ` Chris Murphy
2014-04-23 15:02 ` Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes Andreas Reis
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=5356B1ED.8060608@gmail.com \
--to=andreas.reis@gmail.com \
--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).