From: Andreas Reis <andreas.reis@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Bug:
Date: Fri, 25 Apr 2014 02:04:51 +0000 (UTC) [thread overview]
Message-ID: <loom.20140425T035109-565@post.gmane.org> (raw)
In-Reply-To: pan$df664$93c6c4b1$b586c2f$c5ce83c7@cox.net
Duncan <1i5t5.duncan <at> cox.net> writes:
> Plus, either way you can report back the results and then we'll
know
> whether it's safe to recommend btrfs check for the next report,
or not.
> =:^)
Well this is just bloody brilliant.
I did btrfs check --repair with from integration and a bunch of
fixes on this list applied. Failed at the same assert, but
otherwise left the partition unchanged, ie. mountable.
So as planned, thinking I have a relatively fresh backup of the
whole partition (via partclone.btrfs), I go on restoring it to
get rid of the errors.
partclone does its thing, the restored partition mounts, text
files are properly readable (!) and btrfs check reports no
errors.
Then on reboot, the kernel (residing on another partition)
instantly crashes: "Input/Output error".
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.
Oh, and upon accessing any of said binaries, dmesg prints a BTRFS
info that csum failed. But only for binaries.
Yay. No idea how to proceed from here, but I guess this might not
necessarily be related to btrfs. Certainly doesn't make me want
to recommend it in the foreseeable future, though.
next prev parent reply other threads:[~2014-04-25 2:10 UTC|newest]
Thread overview: 50+ 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 ` Andreas Reis [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2019-08-05 2:42 BUG, Su Yanjun
2016-07-24 13:46 Bug: "git log --format='format:%+s%+b'" doesn't insert newline before body Ilya Tumaykin
2016-07-25 6:55 ` Bug: Beat Bolli
2015-04-10 18:27 Bug? Barclay Jameson
2014-02-17 10:28 bug? Dirk Winning, junidas GmbH
2014-02-17 14:51 ` bug? Pasi Kärkkäinen
2013-11-20 22:18 BUG?? Bruno Bruzzano
2013-11-21 12:02 ` BUG?? Luiz Augusto von Dentz
2013-11-21 14:07 ` BUG?? Bruno Bruzzano
2013-11-21 14:17 ` BUG?? Bruno Bruzzano
[not found] <8E0A14A4C9B95B459AE214584119C1EB3BC909B3@Hal.ad.unb.ca>
2013-01-28 16:37 ` bug? Mathieu Desnoyers
2013-01-23 20:09 bug? Yang Wang
2012-11-23 10:32 Bug? Dirk Winning
2012-11-23 16:46 ` Bug? George Dunlap
2012-04-21 12:53 bug? Thomas Weber
2012-04-24 15:26 ` bug? Josef Bacik
2012-04-24 15:47 ` bug? Thomas Weber
2011-11-23 9:18 Bug? Kormos 'Morc' Gábor
2012-03-22 11:07 ` Bug? Kormos 'Morc' Gábor
2010-02-26 11:15 Bug ;( Ян Программист
2009-08-12 22:07 bug: Dennis Gilmore
2008-08-23 16:17 BUG? Mateyko
2008-08-25 21:35 ` BUG? Luis R. Rodriguez
2007-04-01 13:39 Bug? Sascha Curth
2007-04-01 13:54 ` Bug? Michal Piotrowski
2005-05-19 6:25 bug? Holub Zoltan
2005-05-19 6:25 ` bug? Rudolf Marek
2003-10-08 18:08 BUG ? :) =?unknown-8bit?q?Jos=E9?= Mans
2003-10-08 19:07 ` Alex Zarochentsev
2003-07-17 23:40 Bug? WebExplode.com
2003-06-30 10:15 Bug? Hrvoje Habjanic
2003-03-17 14:06 bug ? Andreas Westin
2002-05-21 9:48 BUG? alex-n
2002-05-21 10:14 ` BUG? Wilfried Weissmann
2001-12-31 18:09 bug ? Klaus Zerwes
2001-12-31 18:51 ` Stephan von Krawczynski
2002-01-05 11:44 ` Klaus Zerwes
2002-01-05 15:37 ` Stephan von Krawczynski
2002-01-02 14:03 ` Simon Richter
2001-12-08 0:31 bug?? wolvie_cobain
2001-12-07 10:33 Bug? Ian Molton
2001-12-07 10:56 ` Bug? DevilKin
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.20140425T035109-565@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.