On 12/19/2017 09:34 AM, Chris Murphy wrote:
On Sun, Dec 17, 2017 at 8:07 PM, Su Yue <suy.fnst@xxxxxxxxxxxxxx>
wrote:
Hi,
On 12/18/2017 10:50 AM, Chris Murphy wrote:
This is v4.14.
I've filed a bug which contains the build steps, versions. It's
crashing on all volumes I try it on so far.
It was fixed by Qu's patch btrfs-progs: backref: Allow backref walk
to handle direct parent ref which is available on his github
https://github.com/adam900710/btrfs-progs/tree/lowmem_fix
OK that fixed the crashing problem on all tested volumes. One volume
so far has a bunch of these:
ERROR: data extent[1218774720512 167936] backref lost
Did you apply all patches on this branch?
If only the patch mentioned above is applied, you can try another
patch named
btrfs-progs: lowmem check: Fix false backref lost warning for keyed
extent data ref
which exists in same branch.
Otherwise, it seems a bug of lowmem check. Would you please
provide some dump of btrfs-debug-tree?
# btrfs-debug-tree /$device |\
grep -C10 1218774720512
You can erase filenames if you think they are private.
With the same numbers for each line. Is that fixed in kdave devel
branch? Or pending? All commits in this brach are pending.
Thanks,
Su
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
