Marc-Christian Petersen wrote:
> after 2 weeks of testing i think i've found a bug in 2.4stable6.
> After mke2fs -j /dev/hda10, mounting, squid -z and using squid for ~ 20-30
> minutes i get the following syslog error message:
>
> kernel: EXT3-fs warning (device ide0(3,10)): ext3_unlink: Deleting
> nonexistent file (97947), 0
> kernel: EXT3-fs error (device ide0(3,10)): ext3_readdir: bad entry in
> directory #16369: rec_len %% 4 != 0 -
> offset=0, inode=909324340, rec_len=26209, name_len=49
This is not a Squid caused problem. Most likely a hardware problem, but could
also be a bad kernel.
> This is not ext3 related, nor is it a bug in my kernel, cause i've tested
> it wirh squid 2.4stable4, works great, no errors on ext3fs. My partition,
> harddisk isn't broken. Also i've moved squid cache partition to another
> partition, same error occurs, the former squid-partition works if i use any
> other program on that partition.
Any errors reported by the filesystem in your syslog/messages is by
definition kernel or hardware problems.
The fact that you don't receive these using 2.4.STABLE4 is purely
coincidental.
Regards
Henrik Nordström
Squid Developer
Received on Thu Apr 11 2002 - 05:42:07 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:07:31 MST