-
Notifications
You must be signed in to change notification settings - Fork 69
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
bcachefs journal update failure: infinite loop when moving to v2 structure #189
Comments
running fsck manually did not give any result either:
.... and bcachefs hangs (at 100% cpu usage) and eats 8GB of ram ... |
It seems it's the same for me:
dmesg also has similar errors. If I can provide any useful info for debugging, please let me know. |
looks like temporaly reverting didn't work any longer:
... so I hope it could be fixed soon, as there is no way to read the data stored on it :s |
@jpsollie there is: I am able to mount fs with |
The error slightly changes with the latest revision (
|
Thanks to the the latest updates I managed to push a non-damaged bcachefs to the latest version:
And then I mounted without nochanges,norecovery (and let fsck do its job), and I saw this:
so now the 3rd time:
...and I guess it's working now! |
|
Ah, I now get it: another undamaged disk. Anyway, I've recreated my filesystem. Let the fun continue :) What is curious is that it was pretty badly damaged: it refused to mount in |
Guess the first versions actually destroyed your journal and fsck is not capable of recovering it. |
I think that's something an automated CI can do:
|
I'm not sure it's that screwed up/destroyed tbh. The journal read seems to be fine and I can still mount and access the data by just adding
This output was from a run with the most recent commit; 641f517 |
On my machine 79847e4 works fine but 8a8844c have trouble adding/removing decvices. when normal mounting (no option specified), I have these kernel messages:
when trying to add another device,
This situation still exsits NOW (e49b2fc, the current HEAD) |
Fixing ticket #188 introduces another issue:
additionally, there's a kworker/u64 thread named btree_update with 100% cpu useage.
bcachefs superblock layout:
The text was updated successfully, but these errors were encountered: