id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
144	incident writer must survive disk-full situations	Brian Warner		"[http://allmydata.org/trac/tahoe/ticket/871 tahoe#871] is about Tahoe surviving a disk-full condition gracefully. One requirement for that is for Foolscap to handle it too. Specifically, Tahoe wants to respond to a soft-limit excursion (i.e. space-available drops below reserved_limit) by emitting a high-severity foolscap log event, which will show up as an Incident and be available for operator inspection later.

We just need to make sure that the incident writer ({{{log.setLogDir()}}}) will survive {{{IOError}}} when it attempts to write an incident to disk. The incident should remain in memory, but the on-disk copy should be abandoned. Further logging calls (especially connections from {{{flogtool tail}}}) must continue to work normally.
"	defect	closed	major	0.6.0	logging	0.4.1	fixed