jstahl80 wrote:

>> With databases, doesn't really matter which
>> database software your using, if you run out of disk space, then all
>> bets are off.
>>
>
> Of course, a full hdd is bad, but should that blow up the database?
> The Server should shutdown the database and return some eror messages
> to the clients, but not corrupt the DB file! Why are there
> transactions etc.? Not to throw away what failed and restart at the
> last good point?
>

Agreed. As long as you run with ForcedWrites=ON the database
shouldn't go bad - the disk image should alway be "consistent".
Is "no disk space" the real problem, or is there some other things
going on as well?

--
Aage J.