From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Laurent Bonnaud <L.Bonnaud@laposte.net>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Lukas Pirl <btrfs@lukas-pirl.de>, <linux-btrfs@vger.kernel.org>,
<calestyo@scientia.net>
Subject: Re: bad extent [5993525264384, 5993525280768), type mismatch with chunk
Date: Mon, 14 Dec 2015 08:53:33 +0800 [thread overview]
Message-ID: <566E130D.105@cn.fujitsu.com> (raw)
In-Reply-To: <566ADBF6.9090507@laposte.net>
Laurent Bonnaud wrote on 2015/12/11 15:21 +0100:
> On 04/12/2015 01:47, Qu Wenruo wrote:
>
>> [run btrfsck]
>
> I did that, too with an old btrfsck version (4.0) and it found the following errors.
> Then I did a btrfsck --repair, and I have been able to complete my "du -s" test.
> The next step will we to run a "btrfs scrub" to check if data loss did happen...
Glad to hear that btrfsck --repair can fix it.
It seems to be space cache problem, and normally mount with -o
clearcache should handle it.
But btrfsck --repair should also handle it well.
Thanks,
Qu
>
> # btrfsck /dev/sdb1
> Checking filesystem on /dev/sdb1
> UUID: f6d4db2e-962b-42db-87b1-35064a4d38e0
> checking extents
> checking free space cache
> block group 314635714560 has wrong amount of free spacefailed to load free space cache for block group 314635714560
> There is no free space entry for 353290420224-353290764288
> There is no free space entry for 353290420224-353827291136
> cache appears valid but isnt 353290420224
> There is no free space entry for 541732175872-541732208640
> There is no free space entry for 541732175872-542268981248
> cache appears valid but isnt 541732110336
> Wanted bytes 32768, found 262144 for off 1008273178624
> Wanted bytes 536625152, found 262144 for off 1008273178624
> cache appears valid but isnt 1008272932864
> block group 1475887497216 has wrong amount of free spacefailed to load free space cache for block group 1475887497216
> block group 1823242977280 has wrong amount of free spacefailed to load free space cache for block group 1823242977280
> There is no free space entry for 1827001073664-1827002810368
> There is no free space entry for 1827001073664-1827537944576
> cache appears valid but isnt 1827001073664
> There is no free space entry for 1969305501696-1969305518080
> There is no free space entry for 1969305501696-1969842290688
> cache appears valid but isnt 1969305419776
> There is no free space entry for 2021381947392-2021381963776
> There is no free space entry for 2021381947392-2021918769152
> cache appears valid but isnt 2021381898240
> There is no free space entry for 2027287478272-2027287724032
> There is no free space entry for 2027287478272-2027824349184
> cache appears valid but isnt 2027287478272
> There is no free space entry for 2143889227776-2143889244160
> There is no free space entry for 2143889227776-2144426000384
> cache appears valid but isnt 2143889129472
> found 1977224107644 bytes used err is -22
> total csum bytes: 1925245108
> total tree bytes: 5773115392
> total fs tree bytes: 3504685056
> total extent tree bytes: 156975104
> btree space waste bytes: 780048699
> file data blocks allocated: 1971884707840
> referenced 1971875930112
> btrfs-progs v4.0
>
next prev parent reply other threads:[~2015-12-14 0:54 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 21:51 bad extent [5993525264384, 5993525280768), type mismatch with chunk Christoph Anton Mitterer
2015-11-12 22:23 ` 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 [this message]
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=566E130D.105@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=L.Bonnaud@laposte.net \
--cc=btrfs@lukas-pirl.de \
--cc=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).