Jesse Norell <[EMAIL PROTECTED]> said: [snip] > We only have about 5.5-6GB of actual data in our dbmail database, > but usage keeps growing over time, eventually filling the 18GB > available disk space. We ended up running periodic vacuum fulls > from cronjobs (twice a month lately), and that does drop the used > disk space down some, but it does continue to grow.
What happens when the disk fills up? Some systems are designed to grow until they fill their bounds, and only then begin to recycle space internally. For example, this is often what makes Java apps seem slow; by default, Java will consume memory until an allocation fails, at which point it runs its GC. The problem is that by the time an allocation fails, you're hundreds of megabytes into swap and other programs can't get memory, either. In the original design, this made sense because Java was meant to be the sole application on a set top box running on a Java OS. Aaron --
