-
Notifications
You must be signed in to change notification settings - Fork 70
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
dirent points to inode that does not point back
- inconsistency detected - emergency read only
#718
Comments
I still have |
Curious about the 'dirent points to inode that does not point back' subject? It doesn't match the rest of the report. I just pushed "bcachefs: Convert for_each_btree_node() to lockrestart_do()" to the testing branch to fix the SRCU warning. |
The subject line is a quote of what's in |
Not sure how related this is but I started consistently receiving the same error when starting steam. Error message:
Versions: |
You guys running online fsck? I just hit it for the first time last night, after running online fsck. |
Yes |
I was also running online fsck, during boot. |
yeah, I see the bug - when we find an unlinked inode we're not checking if it's still open (because if it's not an online fsck, why would it be?) this'll be tricky to fix, because vfs inodes are indexed by subvolume, and we only have the snapshot id in fsck |
Btw, is it expected that background compression hits more bugs like these, or was that just a coincidence? |
background compression wouldn't have anything to do with this, no |
I'm running bcachefs as a root filesystem on an Archlinux desktop. I just updated to kernel
6.10.0-arch1-2
. I can boot fine, but after running for a few minutes I get errors like:Digging a bit via
sudo dmesg | grep bcachefs
gives:I tried
sudo mount -o fsck,fix_errors,remount,rw /
but that doesn't seem to do anything.My bcachefs filesystem lives on
/dev/nvme0n1p3
for foreground writes and as a promote target, and an/dev/sdc1
(a hard disk) for background writes:Update: I booted from a USB stick. Running fsck multiple times in a row keeps finding problems to fix, weirdly enough.
I'm turning background compression off, just to make the system simpler and reduce the 'surface' of things that can go wrong.
Next update: have booted my normal system again. Running fsck multiple times does not keep finding problems. It's stable so far. Perhaps it randomly fixed itself, or turning off background_compression did the trick? I'll be monitoring.
The text was updated successfully, but these errors were encountered: