On 2020-05-21, Qu Wenruo wrote: > Btrfs check hasn't add such restrict check yet, and btrfs scrub doesn't > check the tree contents. > > Furthermore, from the bit, it looks like a memory bitflip, and it is > definitely caused in older kernels which doesn't has such comprehensive > check. Running rsync on the entire file system should trigger tree-checker, if there are other damaged inodes, right? > If it's a memory bitflip, it's highly recommended to run a full memtest > to ensure your memory is OK. I'll do that. > To recover your data, it can be done by removing the offending inodes > with older kernel. > > The inode can be located using the inode number provided in the dmesg. sudo find / -inum 55495 -print gave me /vserver To remove the inode, I run sudo mkdir /vserver2 sudo cp -a --reflink /vserver /vserver2 sudo rm /vserver sudo mv /vserver2 /vserver correct? Joerg
