Re: 2.3STABLE - stability issues

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Fri, 08 Sep 2000 12:04:43 +0200

Andres Kroonmaa wrote:

> did I say that?
> Is there much difference if we talk about another disk or partition?

If you consider recoverability after a disk has crashed, or the
possibilities that someting unrelated causes the disk to be full then
yes it is a big difference. If it resides in a properly dimensioned area
where nothing else has access then the likelyhood that for a disk full
condition is quite small.

> Henrik, I don't get you. Do you object my proposal as pointless?

Not pointless, only that there is ways to configure the system to make
sure it never happens within a reasonable probability.

> I feel you didn't get me.

I did. I only did not express my self well enough.

> My major point was that squid should recover on its own from disk full
> condition.

Exactly, and what I meant to write on the disk space was more like this:

Change Squid to monitor the disk space availability as one parameter
when maintaining the cache content. If free disk space gets below the
configured minimal amount then stop swapouts and start deletetion of
objects to compensate for the fact. This could optionally even be the
way Squid decides the cache size.

And due to being tired I did not consider swap.state.clean. The
following additions to the above is required:

Writing to all the log files should be changed to ignore disk full
conditions, with an option to not ignore the error for access.log and
cache.log.

If a write error is seen on swap.state then stop any further writes to
that swap.state file and schedule a swap.state.clean write after
removing some objects. No further swapouts should be made in this
cache_dir until a swap.state.clean was done sucessfully.

If a disk full condition is detected while writing swap.state.clean then
abort the writeout and reschedule it after first removing some objects.
If this is seen repeatedly then remove the current swap.state prior to
write swap.state.clean to recover from the situation where it is
swap.state which has filled the drive.

/Henrik
Received on Fri Sep 08 2000 - 04:13:54 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:12:36 MST