3 ms·
In their earlier days, the ENOSPCE bug corrupts the filesystem. If you do a heavy random write workload, it fills up the disk pretty quickly and require a re-b
by j16sdiz 5y ago
In their earlier days, the ENOSPCE bug corrupts the filesystem.
If you do a heavy random write workload, it fills up the disk pretty quickly and require a re-balance _before_ ran out of space.
Of cause you can do nocow on those files, but than it lost all the checksuming/snapshotting features.