From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: kernel 3.8.8: btrfs still crashes on boot when it can't replay a log
Date: Thu, 16 May 2013 08:09:18 -0700 [thread overview]
Message-ID: <20130516150918.GB26762@merlins.org> (raw)
I've reported this bug a few times over different kernel versions over the
last year now, and unfortunately it's still not fixed as of 3.8 (yes, I know
3.9 is out, I'm just about to switch).
What happens as far as I know:
I have btrfs on top of dmcrypt on an SDD.
The SSD on occasion seems to just hang, so I have to power cycle my laptop.
I can't say how much the SSD did and did not write before stopping to work.
Then, maybe one time out of 2 or 3, btrfs crashes when I reboot and it tries
to replay the log.
I'm then forced to do this from emergency boot media:
gandalfthegreat:~# btrfs-zero-log /dev/mapper/root
Check tree block failed, want=64855564288, have=14954667565421255623
Check tree block failed, want=64855564288, have=14954667565421255623
Check tree block failed, want=64855564288, have=7474503720151340134
Check tree block failed, want=64855564288, have=14954667565421255623
Check tree block failed, want=64855564288, have=14954667565421255623
read block failed check_tree_block
The last bits of the crash before I zero the log:
http://marc.merlins.org/tmp/btrfs-3.8.8.jpg
Still issues with btrfs_numb_copies.
This has been going on for over a year now, not very pleasant :)
Is there no way you can corrupt logs in a test lab and reproduce this?
Or is it still known to happen due to missing code that decides whether a log is corrupt
and whether to discard it before the code reads it and crashes?
If so, could you add this to the list of things to fix to make btrfs a bit
less scary to others? :)
(and of course more production ready, this repeated problem would kill any
server it happens on)
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next reply other threads:[~2013-05-16 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 15:09 Marc MERLIN [this message]
2013-05-17 15:48 ` kernel 3.8.8: btrfs still crashes on boot when it can't replay a log Marc MERLIN
2013-05-17 16:54 ` Josef Bacik
2013-05-18 1:25 ` Marc MERLIN
2013-05-18 1:51 ` Josef Bacik
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=20130516150918.GB26762@merlins.org \
--to=marc@merlins.org \
--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