K900

This is fixed in master now.

I've had this happen on a dual stack system where the Pi was only reachable on IPv4, which confused Windows somehow.

Same thing here, also on 6.11-rc4, didn't get those on 6.11-rc1, so presumably something broke between those?

Running `bcachefs data job rewrite_old_nodes` gives me ``` [ 980.251423] bcachefs (e0d3a180-f858-46c8-9186-563c88cbd165): bch2_btree_update_start(): error EIO [ 980.252748] bcachefs (e0d3a180-f858-46c8-9186-563c88cbd165): bch2_btree_update_start(): error EIO [ 980.253541] bcachefs (e0d3a180-f858-46c8-9186-563c88cbd165): bch2_btree_update_start(): error EIO [...

fsck does not seem to help here :(

OK, I think I figured out what's happening with the fix at least: every offline fsck tries to reapply the journal, runs into the broken journal entries, fixes _one_ of...

Actually, never mind, looks like the fsck is what's creating the journal entries, because there's always only one of them according to `bcachefs list_journal`.

Also, I just tried updating to 6.11-rc5 and that doesn't seem to change anything.

OK so I started looking at what changed and found https://github.com/koverstreet/bcachefs/commit/d97de0d017cde0d442c3d144b4f969f43064cc0f and https://github.com/koverstreet/bcachefs/commit/8ed823b19214e403ca485532f48c0e02035021ae, which seem to touch these code paths. Reverting those two gets things back to normal again. I'm...

Confirmed that just reverting https://github.com/koverstreet/bcachefs/commit/8ed823b19214e403ca485532f48c0e02035021ae does not fix it, and I'm not qualified enough to revert specifically https://github.com/koverstreet/bcachefs/commit/d97de0d017cde0d442c3d144b4f969f43064cc0f.