From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: btrfs still core dumps
Date: Tue, 19 Nov 2013 19:27:10 -0800 [thread overview]
Message-ID: <20131120032710.GN6696@merlins.org> (raw)
Here is another way in which btrfs-tools crashes if it sees things it
doesn't like.
Is anyone interested in those, or not really?
gandalfthegreat:/tmp# btrfs-find-root /dev/mapper/ssdcrypt
Check tree block failed, want=20971520, have=10422900740180685247
Check tree block failed, want=20971520, have=10422900740180685247
Check tree block failed, want=20971520, have=9351833364687311396
Check tree block failed, want=20971520, have=9351833364687311396
Check tree block failed, want=20971520, have=9351833364687311396
read block failed check_tree_block
Couldn't read chunk root
Segmentation fault (core dumped)
btrfs-tools 0.19+20130705-3
--
"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/ | PGP 1024R/763BE901
next reply other threads:[~2013-11-20 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 3:27 Marc MERLIN [this message]
2013-11-27 4:57 ` btrfs still core dumps Eric Sandeen
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=20131120032710.GN6696@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;
as well as URLs for NNTP newsgroup(s).