Hi, so I had bad memory and before I realized it and removed it btrfs took some damage. Now I have this:
|ls -lh crap/ |ls: cannot access 'crap/2f3f379b2a3d7499471edb74869efe-1948311.d': No such file or directory |ls: cannot access 'crap/454bf066ddfbf42e0f3b77ea71c82f-878732.o': No such file or directory |total 0 |-????????? ? ? ? ? ? 2f3f379b2a3d7499471edb74869efe-1948311.d |-????????? ? ? ? ? ? 454bf066ddfbf42e0f3b77ea71c82f-878732.o and in dmesg I see: | BTRFS critical (device sda4): invalid dir item type: 33 | BTRFS critical (device sda4): invalid dir item name len: 8231 `btrfs check' (from v4.14.1) finds them and prints them but has no idea what to do with it. Would it be possible to let the check tool rename the offended filename to something (like its inode number) put it in lost+found if it has any data attached to it and otherwise simply remove it? Right now I can't remove that folder. Sebastian -- 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
