Interestingly enough we had a similar issue (I think!) last weekend. First time ever I enabled the DB cleaning and optimizing options, hit run job, no less than 2 minutes later the server filesystem filled (we’re talking 130G). Server crashed, couldn’t restart http – we had a pretty long outage. Still not sure what caused this but it does seem sort of coincidental timing.
