Op 09-03-2020 om 17:39 schreef Arun Persaud:
Hi
[...]
That's strange.
As btrfs check selftest can detect such inode generation mismatch and
repair it.
If btrfs-progs failed to repair it, you can delete that inode manually
using older kernel.
We had similar problems, but many files with invalid creation date. As
it was our boot partition we could only fix using old kernel to boot and
recreating the files.
https://lore.kernel.org/linux-btrfs/36d45e31-f125-4b21-a68e-428f807180f7@xxxxxxxxx/
`find -inum 131072` can locate that inode.
not sure how to delete it afterwards...
But before you delete it, please provide the following dump for us to
further debug the problem.
# btrfs ins dump-tree -b 14720090112 /dev/sda2
sure, I can also wait a bit longer before fixing this, since I can at
the moment always boot the old kernel.
I ran the command using the old kernel (since I had that one booted). I
then rebooted into the emergency system of the new kernel and ran again.
Afterwards I went back to the working system (old kernel). Output is
attached. First and second run gave the same output, the third run gave
a lot less output?!
Please note that, the dump will contain filenames, feel free to remove
such filenames.
I didn't see any file names in the output...
HTH
Arun
