[ILUG] file size strangeness

[P at draigBrady.com]

Cian Cullinan wrote:
> On Wed, 22 Sep 2004 21:45:11 +0100, p at draigbrady.com <p at draigbrady.com> wrote:
> 
>>Hmm there is a difference between the blocks used and the file size.
>>I would guess that some program had access_log open, thus
>>keeping a hold on the blocks even if the file is truncated etc.
>>by another process. lsof /var/log/httpd/access_log should tell
>>you if some process has it open, and restarting that processes
>>should free the blocks up?
>>
> 
> Point taken about file-size and blocks-used not being the same thing,
> but I from what I read this normally means file size is larger than
> blocks used, which is the opposite of what I'm seeing.
> "lsof /var/log/https/access_log" shows this file being accessed by
> multiple instances of httpd which seems fair enough. The older log
> files access_log.1,2,3 etc. also have this sizing issue though, and
> none of those are being currently accessed, they're just older
> rotated-out log files. So if it was an issue of some program holding
> the file open and holding onto blocks, it shouldn't be an issue for
> these older files.

That is confusing, though plausible if access_log was renamed to
access_log.num which multiple instances of httpd might still be
holding open? Anyway restart httpd if you can and report back.
It also could be a filesystem bug triggered by a full filesystem?
What filesystem are you using?

-- 
Pádraig Brady - http://www.pixelbeat.org
--- Following generated by rotagator ---

To display a quick calendar on the console:
   cal -3
--