From: Zach Fuller <conicawd@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs Check - "type mismatch with chunk"
Date: Thu, 24 Dec 2015 13:15:22 -0600 [thread overview]
Message-ID: <CACRRrm9SwfDzqHNpWjAGniuu6HDu5wo3vW_ETdzijrdYm7YGGw@mail.gmail.com> (raw)
I am currently running btrfs on a 2TB GPT drive. The drive is working
fine, still mounts correctly, and I have experienced no data
corruption. Whenever I run "btrfs check" on the drive, it returns
100,000+ messages stating "bad extent [###, ###), type mismatch with
chunk". Whenever I try to run "btrfs check --repair" it says that it
has fixed the errors, but whenever I run "btrfs check" again, the
errors return. Should I be worried about data/filesystem corruption,
or are these errors meaningless?
Here are the links to the output of "btrfs check"
(https://app.box.com/s/z2c4ikp6lsn7siezafkth3amo27acs4o) and "btrfs
check --repair"
(https://app.box.com/s/tgg3c4dpfas1wulk30zpudw4mt4bvwoa)
Also, whenever I run btrfs scrub on the drive, it says there are no errors.
I see that there have been other posts on the mailing list with this
same error, such as this one
(https://www.mail-archive.com/linux-btrfs%40vger.kernel.org/msg48325.html).
I have my data backed up on 2 different drives, so I can afford to
lose the entire btrfs drive temporarily.
Here is some info about my system:
$ uname -a
Linux comp 4.2.5-1-ARCH #1 SMP PREEMPT Tue Oct 27 08:13:28 CET 2015
x86_64 GNU/Linux
$ btrfs --version
btrfs-progs v4.3.1
$ sudo btrfs fi show
Another drive...
Label: 'backup' uuid: 1a160f37-7206-43f9-9285-6217ee97a665
Total devices 1 FS bytes used 1.53TiB
devid 1 size 1.82TiB used 1.54TiB path /dev/sdc1
$ sudo btrfs fi df /backup
Data, single: total=1.53TiB, used=1.53TiB
System, DUP: total=32.00MiB, used=224.00KiB
Metadata, DUP: total=3.50GiB, used=2.36GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
Drive Mounting Options from /etc/fstab:
LABEL=backup /backup btrfs noatime,compress=lzo,autodefrag 0 0
next reply other threads:[~2015-12-24 19:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 19:15 Zach Fuller [this message]
2015-12-24 21:27 ` Btrfs Check - "type mismatch with chunk" Christoph Anton Mitterer
2015-12-24 23:41 ` Duncan
2015-12-25 5:28 ` covici
2015-12-25 8:06 ` Duncan
2016-01-02 5:12 ` Christoph Anton Mitterer
2016-01-05 15:34 ` Duncan
2016-01-05 18:54 ` Christoph Anton Mitterer
2016-01-05 19:01 ` Martin Steigerwald
2015-12-27 4:01 ` Christoph Anton Mitterer
2015-12-29 0:08 ` Zach Fuller
2015-12-29 4:16 ` Duncan
2015-12-29 4:42 ` Christoph Anton Mitterer
2016-01-02 10:48 ` Martin Steigerwald
2016-01-02 19:52 ` Henk Slager
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=CACRRrm9SwfDzqHNpWjAGniuu6HDu5wo3vW_ETdzijrdYm7YGGw@mail.gmail.com \
--to=conicawd@gmail.com \
--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).