Re: Disk Full?

Hmm, that's possible. I have already nuked it and -z'ed it
again........but if it happens again, I will df -i and check. Thanks

On Fri, 31 Mar 2000, Jeff Adams wrote:

>
> You are probably out of inodes. Since I'm not sure what flavor of unix
> you are using, I can't give you the exact commands to use. But check your
> inodes, if that's the problem then newfs the disk and specify more inodes.
> Then squid -z to rebuild the cache dir.
>
> Good luck,
> -jeff
>
> On Fri, 31 Mar 2000, Brian wrote:
>
> >
> > I keep finding my squid dying saying the disk is full...........but it
> > doesn't appear to be full:
> >
> > 2000/03/31 17:31:05| Starting Squid Cache version 2.2.STABLE4 for i686-pc-linux-gnu...
> > 2000/03/31 17:31:05| Process ID 12280
> > 2000/03/31 17:31:05| With 1024 file descriptors available
> > 2000/03/31 17:31:05| helperOpenServers: Starting 25 'dnsserver' processes
> > 2000/03/31 17:31:05| Unlinkd pipe opened on FD 30
> > 2000/03/31 17:31:05| Swap maxSize 25088000 KB, estimated 1929846 objects
> > 2000/03/31 17:31:05| Target number of buckets: 38596
> > 2000/03/31 17:31:05| Using 65536 Store buckets, replacement runs every 1 second
> > 2000/03/31 17:31:05| Max Mem size: 16384 KB
> > 2000/03/31 17:31:05| Max Swap size: 25088000 KB
> > 2000/03/31 17:31:05| Rebuilding storage in Cache Dir #0 (DIRTY)
> > 2000/03/31 17:31:05| Rebuilding storage in Cache Dir #1 (DIRTY)
> > 2000/03/31 17:31:05| Rebuilding storage in Cache Dir #2 (DIRTY)
> > 2000/03/31 17:31:05| Rebuilding storage in Cache Dir #3 (DIRTY)
> > 2000/03/31 17:31:05| /var/spool/squid5/swap.state.new: (28) No space left on device
> > FATAL: storeDirOpenTmpSwapLog: Failed to open swap log.
> > Squid Cache (Version 2.2.STABLE4): Terminated abnormally.
> > CPU Usage: 0.050 seconds
> > Maximum Resident Size: 0 KB
> > Page faults with physical i/o: 243
> >
> > [root@constellation squid]# df
> > Filesystem 1k-blocks Used Available Use% Mounted on
> > /dev/sda7 1011928 335980 624544 35% /
> > /dev/sda1 31079 2699 26776 9% /boot
> > /dev/sda5 2016016 178072 1735532 9% /var/log/squid
> > /dev/sda8 1177960 1100176 17944 98% /var/spool/squid1
> > /dev/sdb1 4372108 3982168 167844 96% /var/spool/squid2
> > /dev/sdc1 4372108 3978364 171648 96% /var/spool/squid3
> > /dev/sdd1 8744304 7882912 417200 95% /var/spool/squid4
> > /dev/sde1 8744304 7036288 1263824 85% /var/spool/squid5
> >
> > [root@constellation squid]# grep squid5 /etc/squid/squid.conf
> > cache_dir /var/spool/squid5 7900 16 256
> >
> >
> > Any ideas why it could be doing this?
> >
> > -----------------------------------------------------
> > Brian Feeny (BF304) signal@shreve.net
> > 318-222-2638 x 109 http://www.shreve.net/~signal
> > Network Administrator ShreveNet Inc. (ASN 11881)
> >
> >
>

-----------------------------------------------------
Brian Feeny (BF304) signal@shreve.net
318-222-2638 x 109 http://www.shreve.net/~signal
Network Administrator ShreveNet Inc. (ASN 11881)
Received on Fri Mar 31 2000 - 18:12:22 MST