From: Christian Wimmer <telefonchris@icloud.com>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: is this the right place for a question on how to repair a broken btrfs file system?
Date: Thu, 5 Dec 2019 19:01:33 -0300 [thread overview]
Message-ID: <1DB17C6B-FDFF-406D-BD81-F67A5F4D8493@icloud.com> (raw)
In-Reply-To: <20191205202449.GH4760@savella.carfax.org.uk>
Hi Hugo,
just for your information. I run following command on the backup file:
# btrfs rescue chunk-recover -v /dev/sde1
All Devices:
Device: id = 1, name = /dev/sde1
Scanning: 575601561600 in dev0chunk-recover.c:129: process_extent_buffer: BUG_ON `exist->nmirrors >= BTRFS_MAX_MIRRORS` triggered, value 1
btrfs(+0x6d3b6)[0x56428c4f03b6]
btrfs(+0x6de31)[0x56428c4f0e31]
/lib64/libpthread.so.0(+0x7569)[0x7f351bee9569]
/lib64/libc.so.6(clone+0x3f)[0x7f351bc209ef]
Aborted (core dumped)
Seems to be a bug in the btrfs program.
# uname -a
Linux linux-ze6w 4.12.14-lp151.28.13-default #1 SMP Wed Aug 7 07:20:16 UTC 2019 (0c09ad2) x86_64 x86_64 x86_64 GNU/Linux
# btrfs version
btrfs-progs v4.19.1
Best regards,
Chris
prev parent reply other threads:[~2019-12-05 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 20:00 is this the right place for a question on how to repair a broken btrfs file system? Christian Wimmer
2019-12-05 20:24 ` Hugo Mills
2019-12-05 20:42 ` Christian Wimmer
2019-12-06 0:04 ` Qu Wenruo
2019-12-06 1:32 ` Christian Wimmer
[not found] ` <BD72A51F-A536-428C-9993-91A43C99EE30@icloud.com>
2019-12-06 2:12 ` Qu Wenruo
2019-12-06 2:13 ` Qu Wenruo
[not found] ` <DBA30D34-E186-4359-A8C5-C13C870F1D81@icloud.com>
2019-12-06 3:49 ` Qu Wenruo
2019-12-06 21:28 ` Christian Wimmer
2019-12-05 22:01 ` Christian Wimmer [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=1DB17C6B-FDFF-406D-BD81-F67A5F4D8493@icloud.com \
--to=telefonchris@icloud.com \
--cc=hugo@carfax.org.uk \
--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).