[SQU] Out of inodes?

Hi!

I've been running Squid 2.4DEVEL4 for several weeks without problems but
today stopped working and the following error in cache.log:

2000/10/31 21:08:55| Starting Squid Cache version 2.4.DEVEL4 for
sparc-sun-solar
is2.7...
2000/10/31 21:08:55| Process ID 222
2000/10/31 21:08:55| With 1024 file descriptors available
2000/10/31 21:08:55| Performing DNS Tests...
2000/10/31 21:08:55| Successful DNS name lookup tests...
2000/10/31 21:08:55| DNS Socket created on FD 5
2000/10/31 21:08:55| Adding nameserver 148.213.1.2 from /etc/resolv.conf
2000/10/31 21:08:55| Adding nameserver 148.213.1.9 from /etc/resolv.conf
2000/10/31 21:08:55| Unlinkd pipe opened on FD 10
2000/10/31 21:08:55| Swap maxSize 10223616 KB, estimated 786432 objects
2000/10/31 21:08:55| Target number of buckets: 39321
2000/10/31 21:08:55| Using 65536 Store buckets
2000/10/31 21:08:55| Max Mem size: 131072 KB
2000/10/31 21:08:55| Max Swap size: 10223616 KB
2000/10/31 21:08:55| Store logging disabled
2000/10/31 21:08:55| Rebuilding storage in /cache1 (DIRTY)
2000/10/31 21:08:55| Rebuilding storage in /cache2 (DIRTY)
2000/10/31 21:08:55| Rebuilding storage in /cache3 (DIRTY)
2000/10/31 21:08:55| Using Least Load store dir selection
2000/10/31 21:08:55| Set Current Directory to /cache1
2000/10/31 21:08:55| Loaded Icons.
2000/10/31 21:08:55| Accepting HTTP connections at 0.0.0.0, port 3128, FD
15.
2000/10/31 21:08:55| Accepting ICP messages at 0.0.0.0, port 3130, FD 16.
2000/10/31 21:08:55| Accepting SNMP messages on port 3401, FD 17.
2000/10/31 21:08:55| WCCP Disabled.
2000/10/31 21:08:55| Ready to serve requests.
2000/10/31 21:08:56| diskHandleWrite: FD 8: disk write error: (28) No
space left
 on device
FATAL: Write failure -- check your disk space and cache.log
Squid Cache (Version 2.4.DEVEL4): Terminated abnormally.
CPU Usage: 0.200 seconds = 0.110 user + 0.090 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 0

And this is the inodes usage:

# df -F ufs -o i
Filesystem iused ifree %iused Mounted on
...
/dev/dsk/c0t0d0s3 420783 82065 84% /cache1
/dev/dsk/c0t0d0s4 403655 99193 80% /cache2
/dev/dsk/c0t0d0s5 398054 104794 79% /cache3

And the % of usage:

# df -k
Filesystem kbytes used avail capacity Mounted on
...
/dev/dsk/c0t0d0s3 4131866 3210859 879689 79% /cache1
/dev/dsk/c0t0d0s4 4131866 3213023 877525 79% /cache2
/dev/dsk/c0t0d0s5 4131866 3211308 879240 79% /cache3

In squid.conf (Using Squid's original list based LRU policy):
...
cache_mem 128 MB
reference_age 1 week
cache_dir ufs -1 /cache1 4096 8 256
cache_dir ufs -1 /cache2 4096 8 256
cache_dir ufs -1 /cache3 4096 8 256

I'm experiencing this on a Sun Enterprise 250 with Solaris 7 and 512 MB of
RAM with a 18GB SCSI disk, three 4096GB cache partitions.

Shall I _reformat_ the cache partitions? Has anyone been successful when
he/she experienced this same problem?.

I appreciate your comments and help :)

Raul

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html