Closed Lykos153 closed 1 month ago
this is probably fixed on 6.11; we're no longer storing accounting in the journal (it's got its own btree now), which was the most likely culprit.
Are you able to test on 6.11?
Hey there :) I was away during August. I just got back and tried to mount the FS with 6.11rc5 and indeed, it works! Thank you very much!
It took quite some time (~4 minutes) between check_allocations
and going read-write
, not sure if that is related. EDIT: A consecutive mount was almost instant, so that seems to have been a one-off.
And I still get some soft lockups, but I guess that's a different issue.
FWIW the full log of the successful mount:
the ~4 minutes for check_allocations would've been the disk format upgrade
I just commited a patch to help a bit with that soft lockup - that's a trick one to deal with completely, though
After a couple of days with recurring #717 I am now no longer able to mount the fs at all. Things I did in the meantime:
data_replicas
to 2 (because after every occurrence ofemergency read only
some data would end up corrupt and I hoped thatdata_replicas=2
would increase resilience against that (metadata_replicas
has always been at 3))bcachefs data rereplicate
Unfortunately, during rereplicate, I hit another
emergency read only
and since then the file system seems to be completely borked. Mounting it fails witheven though I am very sure that there are several gigabytes of free space available.
mount.log