Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lost+found directory not able to delete after fsck #805

Open
LostAttractor opened this issue Dec 27, 2024 · 1 comment
Open

lost+found directory not able to delete after fsck #805

LostAttractor opened this issue Dec 27, 2024 · 1 comment

Comments

@LostAttractor
Copy link

LostAttractor commented Dec 27, 2024

I'm using kernel 6.12.
/mnt Is the root of bcachefs, /mnt/Files is a subvolume.

root@NAS ~ [2]# ls -l /mnt/Files/lost+found -a
ls: cannot access '/mnt/Files/lost+found/1174426496': No such file or directory
total 0
drwx------   3 root root 0 Dec 28 02:42 .
drwxrwxr-x+ 16 root root 0 Dec 28 03:22 ..
d??????????  ? ?    ?    ?            ? 1174426496
root@NAS ~ [1]# ls -l /mnt/Files/lost+found/1174426496
ls: cannot access '/mnt/Files/lost+found/1174426496': No such file or directory
root@NAS ~ [2]# rm -r /mnt/Files/lost+found
rm: cannot remove '/mnt/Files/lost+found/1174426496': No such file or directory

I run userspace offline fsck and get four inode_unreachable after unclean shutdown.

errors (size 24):
inode_unreachable                           4               Sat Dec 28 02:42:05 2024
@koverstreet
Copy link
Owner

Fsck in my master branch should correct this now - there was a bug with reattaching inodes that had been deleted in child snapshots.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants