From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Vianney Stroebel <capsule@likwid.fr>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Corrupted btrfs partition (converted from ext4) after balance
Date: Wed, 24 Jun 2015 08:30:54 +0800 [thread overview]
Message-ID: <5589FA3E.4010205@cn.fujitsu.com> (raw)
In-Reply-To: <CAJCQCtQF3H37tKKYWzUW9R3S9h+18Dzpg22hWViAahm2_ttZtQ@mail.gmail.com>
Chris Murphy wrote on 2015/06/23 11:30 -0600:
> On Mon, Jun 22, 2015 at 7:44 PM, Qu Wenruo <quwenruo@cn.fujitsu.com> wrote:
>> Without the full output of btrfsck, it's quite hard to call it a clear bug
>> report if you want to save your data in the corrupted partition.
>
> What I read was that he included everything btrfs check reported,
> which wasn't a lot. It
>
>
>> The command Konsole output "btrfs check /dev/sdb1" outputs :
>> "Checking filesystem on /dev/sdb1
>> UUID: 21873ba7-438a-4fbf-a051-ace28bffd264
>> checking extents"
>> and stops after a few minutes with no other output.
>
> Since he's using btrfs-progs 3.19, I think he should upgrade to
> btrfs-progs 4.1, try check again, and report the complete results.
>
If it stopped without further output, it has a high possibility that
btrfsck encounters a segfault or assert.
If it's assert, backtrace (need to enable at compile time) should be
provided.
If core dump, gdb backtrace is better provided if possible.
Anyway, advice from Chris is quite useful.
Upgrade to latest 4.1 btrfs-progs (better to compile from source) should
solve the two cases above and provide enough information.
Thanks,
Qu
prev parent reply other threads:[~2015-06-24 0:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 23:55 Corrupted btrfs partition (converted from ext4) after balance Vianney Stroebel
2015-06-19 7:53 ` Duncan
2015-06-22 12:40 ` Vianney Stroebel
2015-06-23 1:44 ` Qu Wenruo
2015-06-23 17:30 ` Chris Murphy
2015-06-24 0:30 ` Qu Wenruo [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=5589FA3E.4010205@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=capsule@likwid.fr \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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