Re: [SQU] cache_dir disk space problem

On Tue, 14 Nov 2000, Markus Stumpf wrote:

]> ]> ] If I shutdown squid and do a: echo "" >/cache/swap.state
]> ]> ] will squid delete the old cache files itself?
]> ]>
]> ]> Though it will give Squid an empty cache, the procedure might still lead
]> ]> to problems, if you exceed your file system limit, e.g. the first files
]> ]> from the old cache are small and the first new files are large.
]> ]
]> ]It will NOT give an empty cache. Squid REBUILDS the swap.state in this
]> ]instance.
]>
]> You are right. I am sorry. When did that change? (no answer necessary).
]
]>From my experience yesterday and a look at the code this is NOT TRUE!
]IMHO the FAQ is wrong.
] echo "" >/cache/swap.state
]will give a one byte sized file but squid (2.3ST4) checks for a 0 byte file
]to decide whether to reindex. Otherwise is just reports "0 objects found".

OK, I used "rm swap.state && touch swap.state" --> 0 Byte on all disks.
That would explain why mine reindexed all disks. I don't know what part of
the FAQ you are refering to, but 7.3 says what you said:

 The fastest way to restart with an entirely clean cache is to overwrite
 the swap.state files for each cache_dir in your config file. Note, you
 can not just remove the swap.state file, or truncate it to zero
 size. Instead, you should put just one byte of garbage there. For
 example:

        % echo "" > /cache1/swap.state

Ciao,
Dipl.-Ing. Jens-S. Vöckler (voeckler@rvs.uni-hannover.de)
Institute for Computer Networks and Distributed Systems (RVS)
University of Hanover, Germany; ++49 511 762 4726

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