From: Eric Sandeen <sandeen@redhat.com>
To: Marc MERLIN <marc@merlins.org>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs still core dumps
Date: Tue, 26 Nov 2013 22:57:27 -0600 [thread overview]
Message-ID: <52957BB7.2020300@redhat.com> (raw)
In-Reply-To: <20131120032710.GN6696@merlins.org>
On 11/19/13, 9:27 PM, Marc MERLIN wrote:
> 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
>
Can you try the 3.12 release of btrfs-progs? Lots of stuff
fixed since 0.19 / July 2013.
Still might segfault ;) but please test upstream...
-Eric
prev parent reply other threads:[~2013-11-27 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 3:27 btrfs still core dumps Marc MERLIN
2013-11-27 4:57 ` Eric Sandeen [this message]
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=52957BB7.2020300@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).