inconsistency detected under heavy Nix build loads

[alyssais]

It happens to me very regularly (more often than not) that a couple of hours into a large Nix build, my build fails because my bcachefs filesystem has become read-only.

Example:

Jan 12 15:01:46 sf kernel: bcachefs (nvme0n1p2): inode 296678065 link count underflow
Jan 12 15:01:46 sf kernel: 0 transaction updates for __bch2_unlink journal seq 0
Jan 12 15:01:46 sf kernel:   
Jan 12 15:01:46 sf kernel: bcachefs (nvme0n1p2): inconsistency detected - emergency read only at journal seq 22001751
Jan 12 15:01:46 sf kernel: bcachefs (nvme0n1p2): inode 296678065 link count underflow
Jan 12 15:01:46 sf kernel: 0 transaction updates for __bch2_unlink journal seq 0
Jan 12 15:01:46 sf kernel:   
Jan 12 15:01:46 sf kernel: bcachefs (nvme0n1p2): unshutdown complete, journal seq 22001751

When this happens, I mount bcachefs with -o fsck,fix_errors from the initramfs, and it fixes some stuff, but the same thing happens again next time.

[koverstreet]

What does bcachefs show-super -f errors say?

[koverstreet]

Also, what kernel version? This might be fixed on the master branch