search

google-code-export / lusca-cache

Automatically exported from code.google.com/p/lusca-cache
0 stars 0 forks source link

Dirty cache #88

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. run squid -z
2. run squid
3. Logfile shows

2010/03/02 15:31:50| Rebuilding storage in /proxy1 (DIRTY)

What is the expected output? What do you see instead?
Shouldn't this filesystem be clean?

What version of the product are you using? On what operating system?
LUSCA_HEAD debian 5.0 amd64

Original issue reported on code.google.com by kris%amy...@gtempaccount.com on 2 Mar 2010 at 5:35

GoogleCodeExporter commented 9 years ago 
this is due to the fact that there is no swap.file
it will be created by starting squid, if not exist squid suppose a dirty 
cache_dir 
so this is normal and ok

Original comment by hm@hm.net.br on 6 Mar 2010 at 10:07

GoogleCodeExporter commented 9 years ago 
It should be fine in LUSCA_HEAD now after a clean restart/rebuild has written a 
swap.state logfile.

Original comment by adrian.c...@gmail.com on 24 Mar 2010 at 2:44