Chris Murphy wrote on 2015/06/23 11:30 -0600:
On Mon, Jun 22, 2015 at 7:44 PM, Qu Wenruo <quwenruo@xxxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
