2
1
I think I have been hit by a known bug in btrfs:
https://www.spinics.net/lists/linux-btrfs/msg60984.html
Certainly, the error messages seem similar. If it is the same issue, it seems somewhat unfortunate that the fix for a 2 year old issue hasn't been ported into the V4.9 stable kernel (which is what Debian 9 uses)
I am now in the situation where one of the filesystem inodes has extent problems (as reported by btrfs check
):
root 257 inode 2607184 errors 100, file extent discount
Found file extent holes:
start: 0, len: 81920
It seems there isn't much advice or documentation on how to get out of such a situation (fortunately I do have backups of the filesystem concerned, so worst case could reformat and restore)
It seems btrfs check --repair
just loops printing the same error over and over, without actually fixing it.
Is there any way to fix the existing filesystem, or am I best to recreate it and restore the backup?
Thanks - I went for a similar (but slightly more extreme) option of deleting the subvolume with the problems in. It seems freeing up the inode made the file system check cleanly. If you want to make an answer based on this, I will vote it as correct – Michael Firth – 2018-10-01T18:24:48.280