On 2/13/20 3:02 PM, telsch wrote:
According to the repair log, btrfs-progs doesn't detect it at all. Thus I'm not sure if it's a bug in btrfs-progs or it's just not newer enough. Anyway, you can delete inode 265 manually using older kernel. Thanks, QuThanks for support. Deleting inode 265 manually fixed this mount issue with kernel >= 5.2 for me.
Btw the patches to fix up invalid generations that Qu referred to are in btrfs-progs-5.4.*1*, not 5.4. -h
