* How to repair errors only found with check --mode=lowmem
@ 2017-12-16 15:41 Tom Hale
2017-12-18 1:10 ` Qu Wenruo
0 siblings, 1 reply; 4+ messages in thread
From: Tom Hale @ 2017-12-16 15:41 UTC (permalink / raw)
To: linux-btrfs
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to repair errors only found with check --mode=lowmem
2017-12-16 15:41 How to repair errors only found with check --mode=lowmem Tom Hale
@ 2017-12-18 1:10 ` Qu Wenruo
2017-12-18 7:04 ` Ravi Hale
0 siblings, 1 reply; 4+ messages in thread
From: Qu Wenruo @ 2017-12-18 1:10 UTC (permalink / raw)
To: Tom Hale, linux-btrfs
[-- Attachment #1.1: Type: text/plain, Size: 3181 bytes --]
On 2017年12月16日 23:41, Tom Hale wrote:
> The following shows that errors are found with check --mode=lowmem, but
> are not picked up without lowmem.
Btrfs-progs version please.
Depending on your btrfs-progs version, and the output, it's possible
that they're just false alerts and should be addressed in latest version.
Thanks,
Qu
>
> 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]#
>
> ----------------------------------------
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to repair errors only found with check --mode=lowmem
2017-12-18 1:10 ` Qu Wenruo
@ 2017-12-18 7:04 ` Ravi Hale
2017-12-18 7:17 ` Qu Wenruo
0 siblings, 1 reply; 4+ messages in thread
From: Ravi Hale @ 2017-12-18 7:04 UTC (permalink / raw)
To: Qu Wenruo, linux-btrfs
My bad. 4.14.
--
Tom "Ravi" Hale
Sent from my phone, please excuse brevity
On 18 December 2017 08:10:18 Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>
>
> On 2017年12月16日 23:41, Tom Hale wrote:
>> The following shows that errors are found with check --mode=lowmem, but
>> are not picked up without lowmem.
>
> Btrfs-progs version please.
>
> Depending on your btrfs-progs version, and the output, it's possible
> that they're just false alerts and should be addressed in latest version.
>
> Thanks,
> Qu
>
>>
>> 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]#
>>
>> ----------------------------------------
>>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to repair errors only found with check --mode=lowmem
2017-12-18 7:04 ` Ravi Hale
@ 2017-12-18 7:17 ` Qu Wenruo
0 siblings, 0 replies; 4+ messages in thread
From: Qu Wenruo @ 2017-12-18 7:17 UTC (permalink / raw)
To: Ravi Hale, linux-btrfs
[-- Attachment #1.1: Type: text/plain, Size: 1065 bytes --]
On 2017年12月18日 15:04, Ravi Hale wrote:
> My bad. 4.14.
Well, things get interesting now.
Although there are several new lowmem fixes pending for v4.14.1, the
backref mismatch bug should be addressed in v4.14.
Anyway, would you please try this branch to see if it solves the false
alerts?
https://github.com/kdave/btrfs-progs/commits/devel
If the devel branch still reports error, we still have good enough
sample to dig further.
>> ERROR: extent[691815358464, 11042816] referencer count mismatch
(root: 257, owner: 1869679, offset: 613974016) wanted: 1, have: 2
This is a pretty good sample, small enough to find out what's going on.
Ff devel branch can't help you, would you please dump the output of the
following commands?
# btrfs-debug-tree -t extent /dev/mapper/vg_svelte-home |\
grep -C10 691815358464
# btrfs-debug-tree -t 257 /dev/mapper/vg_svelte-home |\
grep -C20 1869679
Please note that, the 2nd output may contain *FILENAMES*, so feel free
to erase any file name if it's sensitive.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-12-18 7:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-12-16 15:41 How to repair errors only found with check --mode=lowmem Tom Hale
2017-12-18 1:10 ` Qu Wenruo
2017-12-18 7:04 ` Ravi Hale
2017-12-18 7:17 ` Qu Wenruo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox