From: Christoph Anton Mitterer <calestyo@scientia.net>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: bad extent [5993525264384, 5993525280768), type mismatch with chunk
Date: Thu, 12 Nov 2015 22:51:03 +0100 [thread overview]
Message-ID: <1447365063.7045.7.camel@scientia.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
Hey.
I get these errors on fsck'ing a btrfs:
bad extent [5993525264384, 5993525280768), type mismatch with chunk
bad extent [5993525280768, 5993525297152), type mismatch with chunk
bad extent [5993525297152, 5993525313536), type mismatch with chunk
bad extent [5993529442304, 5993529458688), type mismatch with chunk
bad extent [5993529458688, 5993529475072), type mismatch with chunk
bad extent [5993530015744, 5993530032128), type mismatch with chunk
bad extent [5993530359808, 5993530376192), type mismatch with chunk
bad extent [5993530376192, 5993530392576), type mismatch with chunk
bad extent [5993530392576, 5993530408960), type mismatch with chunk
bad extent [5993530408960, 5993530425344), type mismatch with chunk
bad extent [5993531260928, 5993531277312), type mismatch with chunk
bad extent [5993531310080, 5993531326464), type mismatch with chunk
What do they mean? And how to correct it without data loss (cause this
would be critical/precious data)?
Oddly, I've fsck'ed the very same fs last time I've unmounted it (with
no errors)... and now this.
The only difference would be newer kernel and btrfsprogs.
Thanks,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next reply other threads:[~2015-11-12 21:51 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 21:51 Christoph Anton Mitterer [this message]
2015-11-12 22:23 ` bad extent [5993525264384, 5993525280768), type mismatch with chunk Christoph Anton Mitterer
2015-11-13 2:13 ` Qu Wenruo
2015-11-13 2:26 ` Christoph Anton Mitterer
2015-11-13 2:52 ` Qu Wenruo
2015-11-13 3:03 ` Christoph Anton Mitterer
2015-11-13 3:23 ` Qu Wenruo
2015-11-13 3:31 ` Christoph Anton Mitterer
2015-11-13 3:44 ` Christoph Anton Mitterer
2015-11-13 3:57 ` Christoph Anton Mitterer
2015-11-13 7:05 ` Duncan
2015-11-13 9:55 ` Christoph Anton Mitterer
2015-11-13 11:37 ` Christoph Anton Mitterer
[not found] ` <564F48FE.4000400@laposte.net>
2015-11-20 19:24 ` Christoph Anton Mitterer
2015-11-21 0:47 ` Qu Wenruo
2015-11-21 1:08 ` Lukas Pirl
2015-11-22 2:04 ` Qu Wenruo
2015-11-22 6:56 ` Christoph Anton Mitterer
2015-11-23 1:10 ` Qu Wenruo
2015-11-23 18:12 ` Christoph Anton Mitterer
2015-11-24 0:46 ` Qu Wenruo
2015-11-24 1:53 ` Christoph Anton Mitterer
2015-11-24 2:09 ` Qu Wenruo
2015-11-24 2:48 ` Christoph Anton Mitterer
2015-11-24 2:54 ` Qu Wenruo
2015-11-24 3:02 ` Christoph Anton Mitterer
2015-11-24 5:35 ` Qu Wenruo
2015-11-24 18:25 ` Christoph Anton Mitterer
2015-11-25 0:02 ` Qu Wenruo
2015-11-25 0:59 ` Qu Wenruo
2015-11-25 3:35 ` Christoph Anton Mitterer
2015-11-25 4:16 ` Christoph Anton Mitterer
2015-11-24 17:39 ` David Sterba
2015-11-22 10:17 ` Laurent Bonnaud
2015-11-23 1:00 ` Qu Wenruo
2015-11-24 13:15 ` Laurent Bonnaud
2015-11-24 23:46 ` Qu Wenruo
2015-11-25 9:05 ` Laurent Bonnaud
2015-12-03 17:13 ` Laurent Bonnaud
2015-12-04 0:47 ` Qu Wenruo
2015-12-11 13:22 ` Laurent Bonnaud
2015-12-11 14:21 ` Laurent Bonnaud
2015-12-14 0:53 ` Qu Wenruo
2015-12-14 12:47 ` Laurent Bonnaud
2015-12-15 1:16 ` Qu Wenruo
2015-11-24 23:53 ` Qu Wenruo
2015-11-14 1:22 ` Qu Wenruo
2015-11-14 2:29 ` Christoph Anton Mitterer
2015-11-15 1:29 ` Qu Wenruo
2015-11-15 3:24 ` Christoph Anton Mitterer
2016-02-16 0:14 ` Ángel González
2016-02-16 1:38 ` Qu Wenruo
2016-02-16 22:21 ` Ángel González
2016-02-17 7:26 ` Qu Wenruo
2016-02-17 23:56 ` Ángel González
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=1447365063.7045.7.camel@scientia.net \
--to=calestyo@scientia.net \
--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).