jpsollie
jpsollie
what does "bcachefs set-option --version_upgrade (devices)" do?
you could do a bcachefs fsck -v -f (devices) to see whether the upgrading worked correctly if that's ok, your filesystem should work again
if you mount with -o ro,very_degraded, is your data readable?
@koverstreet, @YellowOnion any ideas?
it's definitely a locking issue (very funny to debug), but this may help you: compile the kernel with debug info, and under "hacking options", enable lock debugging: ``` Lock usage...
`` perf_5.10: page allocation failure `` This is weird ... Looks like bcachefs can't get anny additional memory @koverstreet : any comments on this? Looks like the user has plenty...
at mount, bcachefs sometimes needs a lot of time to replay the journal & construct its inner data structures, especially on large devices. How long did you wait before concluding...
what helped (for me): - mount fs ro,nochanges (disadvantage, off course, is that you're stuck with a ro filesystem) - recompile glibc, gcc and kernel from scratch, don't know why...
probably related to #424 , could you recheck with latest version?
bcachefs doesnt support crypto engine yet, as such all checksums are done in software. This will be a nice enchantement, once it becomes stable enough to handle async crypto