From: Tom Hale <tom@hale.ee>
To: linux-btrfs@vger.kernel.org
Subject: How to repair errors only found with check --mode=lowmem
Date: Sat, 16 Dec 2017 22:41:23 +0700 [thread overview]
Message-ID: <abb41cea-93eb-0e35-e9b2-195968fc4fd7@hale.ee> (raw)
The following shows that errors are found with check --mode=lowmem, but
are not picked up without lowmem.
How would I go about fixing errors only reported by lowmem?
----------------------------------------
[manjaro manjaro]# btrfs check --mode=lowmem --progress
/dev/mapper/vg_svelte-home
Checking filesystem on /dev/mapper/vg_svelte-home
UUID: 93722fa7-7e8f-418a-a7ca-080aca8db94b
ERROR: extent[691815358464, 11042816] referencer count mismatch (root:
257, owner: 1869679, offset: 613974016) wanted: 1, have: 2
ERROR: extent[720156536832, 99430400] referencer count mismatch (root:
257, owner: 758215, offset: 1610616832) wanted: 8, have: 379
ERROR: extent[720669147136, 268435456] referencer count mismatch (root:
257, owner: 758215, offset: 4096) wanted: 86, have: 1021
ERROR: extent[720669147136, 268435456] referencer count mismatch (root:
257, owner: 1767807, offset: 4096) wanted: 87, have: 1021
ERROR: extent[726724722688, 64069632] referencer count mismatch (root:
257, owner: 1480823, offset: 99090432) wanted: 1, have: 5
ERROR: extent[737910194176, 134217728] referencer count mismatch (root:
257, owner: 1480726, offset: 268435456) wanted: 1, have: 8
ERROR: extent[738077896704, 134217728] referencer count mismatch (root:
257, owner: 1869696, offset: 402653184) wanted: 5, have: 8
ERROR: extent[744334426112, 268435456] referencer count mismatch (root:
257, owner: 1767802, offset: 0) wanted: 111, have: 294
ERROR: extent[824948670464, 1671168] referencer count mismatch (root:
257, owner: 2000876, offset: 247861248) wanted: 16, have: 26
ERROR: data extent[681550843904 8192] backref lost
ERROR: errors found in extent allocation tree or chunk allocation
cache and super generation don't match, space cache will be invalidated
ERROR: errors found in fs roots
found 172094545920 bytes used, error(s) found
total csum bytes: 165679768
total tree bytes: 3066789888
total fs tree bytes: 2751315968
total extent tree bytes: 112295936
btree space waste bytes: 568660274
file data blocks allocated: 8158426562560
referenced 597269540864
[manjaro manjaro]# btrfs check --repair --progress
/dev/mapper/vg_svelte-home
enabling repair mode
Checking filesystem on /dev/mapper/vg_svelte-home
UUID: 93722fa7-7e8f-418a-a7ca-080aca8db94b
checking extents [.]
Fixed 0 roots.
cache and super generation don't match, space cache will be invalidated
checking fs roots [o]
checking csums
checking root refs
found 172091723777 bytes used, no error found
total csum bytes: 165679768
total tree bytes: 2003206144
total fs tree bytes: 1687732224
total extent tree bytes: 112295936
btree space waste bytes: 346177995
file data blocks allocated: 5952940838912
referenced 474676633600
[manjaro manjaro]#
----------------------------------------
--
Tom Hale
next reply other threads:[~2017-12-16 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 15:41 Tom Hale [this message]
2017-12-18 1:10 ` How to repair errors only found with check --mode=lowmem Qu Wenruo
2017-12-18 7:04 ` Ravi Hale
2017-12-18 7:17 ` Qu Wenruo
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=abb41cea-93eb-0e35-e9b2-195968fc4fd7@hale.ee \
--to=tom@hale.ee \
--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