Jan Schmidt <list.btrfs <at> jan-o-sch.net> writes: > I think you shouldn't. The "errors 400" is reported constantly in > #btrfs, it resolves to REF_ERR_NO_ROOT_BACKREF. There should be a > backref, but I haven't heard of any negative impact. > > If you are curious, you can try to grab the "inspect-internal" patches > for btrfs-progs and use "btrfs inspect-internal resolve-inode 5067" to > see what files are referenced by those inodes (given you are still > running the kernel you used for scrubbing).
Thx Jan, I did not follow your advice but used the btrfs-debug-tree to determine the affected files. After deleting them it has been OK. Interessting thing is, that in one case copying the file has been possible to resolve one of these errors (after deleting the original file of course). Other affected file throw an input/output error when trying to access them. Let me know when I can test some more things. I can offer to run the newest kernels and patches and report any issues!? Thx, Jan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
