-
Notifications
You must be signed in to change notification settings - Fork 73
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
accounting keys with version=0 fix doesn't persist #756
Comments
That report makes it look like we're still generating version=0 keys, and the patch making bkey errors AUTOFIX broke the emergency shutdown paths that would've given us more info. Can you try the current bcachefs-for-upstream branch? |
No change with the current bcachefs-for-upstream (0f25eb4). I get the messages, and the autofixing, on mount, umount, and when looking at filesystem usage. Still no idea where these are generated. |
Is it expected to have accounting keys with btree=(unknown)? |
I've switched to 406358e "bcachefs: Avoid bch2_btree_id_str()" on bcachefs-testing, so I get slightly more detailed error messages:
134217728 is 2^27 Some of the other keys have been staying fixed, and this is the last one. The messages from before the reboot, at umount time:
|
Though if I look for "unknown btree" I find more:
(The btree ids aren't all powers of two, but they all have at least 24 trailing zeroes) The first time I grep there's just one that gets reported in dmesg
|
This seems to have fixed itself with fd034bd (bcachefs-testing)
First time mounting errors (see above), but the next one was successful. There are still unknown accounting keys but they aren't noticed by fsck. |
Closing as I can't reproduce anymore, though let me know if the other unknown keys are of interest. I guess they are kept by design for forward compat reasons and I don't think new ones are being introduced. |
6e44d6e "bcachefs: If we did repair on a btree node, make sure we rewrite it" seemed to address this. |
This issue seems more cosmetic, reporting it because the that fsck code was updated recently
When mounting (with or without -o fsck,fix_errors):
Sometimes during runtime (edit: when I run
bcachefs fs usage
or look at /sys/kernel/debug/bcachefs/99*/btrees/accounting/keys):And again at shutdown:
The text was updated successfully, but these errors were encountered: