[SUMMARY] Netscape proxy and realloccg failure

2007-12-25 9:22:00

Matthew Fansher wrote:-

saw this problem at 77%. Cleaning out the cache has been his solution

in the past.

He also pointed out the NS Proxy Server is what I call "functionally

stable".

K Robson, John Weekley, Kevin Sheehan suggested:-

Check tunefs on the filesystem. I consulted the fellow who created the

partitions, Ivan Dean, and he said he used the defaults for newfs which

gives a minfree of 10%.

Bismark Espinoza and Patrick Pawlak suggested:-

Check the inodes free. The inodes free are 30% and 50% for each

filesystem respectively.

Larry Pazdernik suggested:-

While not sure if specific to our requirement, increment the cache size then

decrement it back to the

original figure. While it looks like "Smoke and Mirrors", it may tickle the

arcane workings of the server and its GC. It may also be just rearranging the

deck chairs :)

Casper Dik and Ivan Dean pointed out:-

The cause for the error is the heavy fragmentation denying the creation of

large files as full blocks consisting of consecutive fragments are required.

Laszlo Ernesto de Miranda Pinto noted:-

I am also seeing this using Squid and x86.

  

Obviously, allocating a large number of files with a wide range of

sizes is not a simple problem. We may have to look at decreasing

the maximum size of file we cache. "The needs of the many outweigh

the needs of the few" in this case. On the other hand, we may

have many small files that may be better not cached. Looking at

the Configuration of the server, it us using a "Derived"

configuration. Unfortunately, it is not clear what this means from

the docs. Perhaps setting the values manually might be a better

option.

Decision:-

1. Weighing up the time it takes to ufsdump and ufsrestore the 2x5GB

partitions using a DDS3 tape,the cache hit ratio and the cost

of repopulating the cache, the most cost-effective, but inelegant,

solution is to newfs the two partitions and recreate the cache

structure. No more fragmentation for a while anyway.

2. Look more closely at the Caching configuration.

This could, however, be a tunnel down which very little light

would shine without a lot of analysis of the caches and the

file size distribution.

Thanks once again to all the sun-managers who responsed.

Regards


--
=========================================================
Gambling: A discretionary tax on | Anthony David
those who were asleep during high | Systems Administrator
school mathematics classes |

Comments

Got something to say?

You must be logged in to post a comment.