After working through a design for maintaining consistency given a disk full condition during a multi-table write (which only occurs with a tx write), I realized that this condition is already managed. Multi-table writes occur both concurrently and during ongoing reads, such as by validation/confirmation and also client/server queries. Full consistency is of course eventual, but all queries produce logical results even in the midst of multi-table writes. So when a single table fails to expand during a write, such as for disk full, all we need to do is stop and report it.