Closed bdarnell closed 6 years ago
Adding this to Jepsen might still make sense for the correctness aspect of this, but we have the infra for doing this in roachtest-land available. The test that comes to mind is
Folding into https://github.com/cockroachdb/cockroach/issues/7882 (the other way than I originally planned to).
Prior to #19447, certain disk errors (the most likely being
ENOSPC
) were not being handled correctly, and we suspect that inconsistent reads could be served after this had happened. We need more testing of our behavior after disk writes have failed.One way to do this would be a process that alternately writes a file to fill up the disk (or maybe just
fallocate()
), waits a bit, then deletes the file (and restarts the cockroach process if it crashed). Maybe this would make sense as a new jepsen nemesis.