*Matt Anglin's words during the TSM Symposium last week don't give me much
hope for a quick fix, i'm losely quoting here "we develop towards things
getting bigger all the time".*
He was talking about making logs smaller if I am not mistaking.

On Fri, Sep 30, 2011 at 5:06 PM, Zoltan Forray/AC/VCU <zforray AT vcu DOT 
edu>wrote:

> I recently expanded the log size from 60GB to 120GB to allow for an
> expected increase in transactions (was deleted 190M objects).
>
> Now that this is over, I need to shrink it back down to 60GB since the
> filespace it is using is shared by the DB and now I get a daily messages
> that the DB is running low on space (89.40% utilized.
>
> So what does it take to do this?   I am guessing that simply changing the
> logsize to 60GB won't just magically reclaim the space....
>
> Server is Linux 6.1.5.10
>
> Zoltan Forray
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>