On 8/12/2013 11:37 a.m., Hussam Al-Tayeb wrote: > I have something like this: > 2013/12/08 00:18:50| Done reading /home/squid swaplog (293760 entries) > 2013/12/08 00:18:50| Finished rebuilding storage from disk. > 2013/12/08 00:18:50| 293760 Entries scanned > 2013/12/08 00:18:50| 0 Invalid entries. > 2013/12/08 00:18:50| 0 With invalid flags. > 2013/12/08 00:18:50| 293760 Objects loaded. > 2013/12/08 00:18:50| 0 Objects expired. > 2013/12/08 00:18:50| 0 Objects cancelled. > 2013/12/08 00:18:50| 0 Duplicate URLs purged. > 2013/12/08 00:18:50| 0 Swapfile clashes avoided. > 2013/12/08 00:18:50| Took 1.00 seconds (294266.73 objects/sec). > 2013/12/08 00:18:50| Beginning Validation Procedure > 2013/12/08 00:18:50| 262144 Entries Validated so far. > 2013/12/08 00:18:50| Completed Validation Procedure > 2013/12/08 00:18:50| Validated 293759 Entries > 2013/12/08 00:18:50| store_swap_size = 18411592.00 KB > 2013/12/08 00:18:50| storeLateRelease: released 0 objects > > This means 1 object (293760-293759 =1) was not validated. > > - Can squid still eventually automatically purge that 1 object from > disk through aging or something? > - Any way to extract through some debug option what that object is? > > Yes I know it is just one file but I would like to keep the cache clean. I dont think your validation algorithm is doing anything at all right now. The actual validation procedure is to open every disk object and verify the details of its existence and size. That takes a relatively long time and is only performed if you start Squid with the -F command line option. Otherwise it is only performed as-needed by live traffic (TCP_SWAPFAIL_MISS gets logged if live validation fails). The 1 difference is a bit odd though. Amos
