> 	What may be happening is that, because file removals or truncations
> don't get sent to the disk immediately, the data is not immediately
> reclaimed and the disk may appear full when it's not. Presumably it
> should catch up within 30 seconds, which is the latency-limit before
> things get flushed. Unless it's broken. 8-)

One would hope that, as the softdep code increases in maturity, it
will do something sane here..  for instance, if there are deferred
deallocations pending when it detects a filesystem full condition, it
could kick them to run immediately and then sleep waiting for them to
complete before returning a disk-full error to userland..

					- Bill