On Thu, Aug 25, 2011 at 2:29 PM, Simon Slavin <[email protected]> wrote:
> I think your overall best strategy here it not to run any system so close > to the margin it's likely to fail. Define some amount of free space for > your system -- for example 10Kb for an embedded system or 1Meg for a desktop > computer -- and if you have less than that amount of space free, take > emergency measures and refuse to accept new data. > A slight elaboration on that: this approach might not suffice on Unix systems. Filesystems on Unix tend to (but not always) have a certain percentage of the space reserved for the superuser (to keep user-space processes from filling up the system, which can lead to all kinds of problems on Unix systems, including (potentially) the inability to log in and fix the problem). e.g. just because your tools report that a 100GB drive still has 10GB free, 5GB of that might not be allocatable to non-root processes. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
