[Server-devel] [XSCE] Has anyone else seen squid swap.state bloat?

[Anish Mangal]

I think this is serious enough to warrant atleast a doc note to have the
squid cache in a different partition as it makes the machine completely
unusable otherwise. I don't think it is maybe the best idea to have it in
library (but rather a separate partition).

Or, as you say, a cron job - but in my case the bloat filled up the hdd in
less than a week.

On Sun, May 8, 2016 at 6:11 PM, Jerry Vonau <me at jvonau.ca> wrote:

>
>
> > On May 5, 2016 at 11:20 PM Anish Mangal <anishmg at umich.edu> wrote:
> >
> >
> > Yesterday, an interesting issue happened. On an older XSCE install, the
> > squid cache bloated over time to create a 300GB swap file and made the
> > server unusable. I was wondering if anyone else may have come across this
> > before?
> >
>
> Yes, squid's model assumes that the cache that lives on a partition all by
> itself with no real consideration for other programs on that partition.
> Think that was the original reason for /library in the first place, maybe
> we should rethink where the content/databases should reside.
>
> > Attached is the munin screenshot showing the increasing disk usage over
> > time. I deleted the file and things are back to normal - for now.
> >
>
> Weekly cron job to do that unattended?
>
> > The xsce git hash is 9a072ead3da91b84e6db896554c50bfa37e7b4e6
> >
> > --
> > Anish
>
> Jerry
>



-- 
Anish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/server-devel/attachments/20160511/4f046a81/attachment-0001.html>