From: Andreas Reis <andreas.reis@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Bug: Partition borked
Date: Fri, 25 Apr 2014 02:43:17 +0000 (UTC) [thread overview]
Message-ID: <loom.20140425T043341-931@post.gmane.org> (raw)
In-Reply-To: loom.20140425T035109-565@post.gmane.org
Andreas Reis <andreas.reis <at> gmail.com> writes:
> Turns out that when I try to run any binary from the restored
> partition (via LiveCD), *every* *single* *one* fails with this
> remarkably expressive error. If I manually replace one with a
> fresh download, I get a SIGBUS crash instead.
Alright, there are corrupt text files too, after all. As well as a
handful or non-corrupted binaries.
Always the same type of btrfs error message though. Interestingly,
the false csum reported stays exactly the same: 2566472073. Also,
btrfs check --init-csum-tree fails with a plethora of backref
errors.
Guess it doesn't matter whether it's the backup or the LiveCD's
kernel (3.13.7) that's at fault, I'm going to have to reinstall
either way.
next prev parent reply other threads:[~2014-04-25 2:43 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
2014-04-23 2:55 ` Duncan
2014-04-25 2:04 ` Bug: Andreas Reis
2014-04-25 2:43 ` Andreas Reis [this message]
2014-04-25 3:03 ` Bug: Partition borked 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=loom.20140425T043341-931@post.gmane.org \
--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).