asnani_satish wrote > This happens when size specified in cache_mem >= cache_dir > Example: > cache_dir aufs /var/spool/squid 1000 32 512 > implies 1000 MB physical disk space allotted for cache in specified > directory > cache_mem 900 MB > cache size to be used by squid which must be less than the size > specified in cache_dir directive. > > Dont forget to restart squid > > We cannot just ignore the error because if this error keeps on occurring > the performance of squid degrades. Are you sure??? i'm getting this error when turning back on a squid system that I had down (out of production for 2 days). My config does not indicate an issue that you advise to be the cause of the error. cache_mem 1 GB cache_dir aufs /cache 65000 16 256 I'm not seeing any issue but the error is rampant at this point 2017/02/02 10:58:59 kid1| /cache/07/49/003749FE 2017/02/02 10:59:00 kid1| DiskThreadsDiskFile::openDone: (2) No such file or directory 2017/02/02 10:59:00 kid1| /cache/05/3E/00053EA0 2017/02/02 10:59:00 kid1| DiskThreadsDiskFile::openDone: (2) No such file or directory 2017/02/02 10:59:00 kid1| /cache/0D/EB/005DEB19 2017/02/02 10:59:00 kid1| DiskThreadsDiskFile::openDone: (2) No such file or directory 2017/02/02 10:59:00 kid1| /cache/02/27/0002273A -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/DiskThreadsDiskFile-openDone-squid-3-5-0-4-tp4668840p4681455.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
