LinuxSA Mailing list archives

Index: [thread] [date] [subject] [author]
  From: Phil Hutton <philhutton@bigfoot.com>
  To  : linuxsa@linuxsa.org.au
  Date: Sun, 16 Apr 2000 12:30:21 +0930

Filesystem Wierdness

Hi...

I have an interesting problem with an ext2 file system.  It seems that the free
inodes count on the filesystem is getting corrupted, which is causing some
problems.

The following messages get dumped to the console (regularly):
---
EXT2-fs error (device ide0(3,5)): ext2_new_inode: Free inodes count
corrupted in group 132
EXT2-fs error (device ide0(3,5)): ext2_new_inode: Free inodes count
corrupted in group 132
EXT2-fs error (device ide0(3,5)): ext2_new_block: Free blocks count
corrupted for block group 7
EXT2-fs error (device ide0(3,5)): ext2_new_block: Free blocks count
corrupted for block group 7
---

The machine is a proxy server running squid, and the partition with problems is
the main cache partition.  After running for 4-5 days the corruption gets bad
enough that the kernel thinks that there are no free inodes, and declares that
the disk is full.  This causes squid to die, and users to get upset.  When this
happens the cache partition must be unmounted, fscked and remounted.  Squid can
then be restarted.

Normally I'd say that this is a hardware problem, but the only problem that
fsck ever finds is block bitmap differences.  If the disk was having problems
I'd expect to see more errors.

I'm including some more information at the end of this message.  Does anyone
have any suggestions as to what may be causing the problem, or how the problem
may be fixed?

- Is squid doing something strange when it unlinks files?
- Is the kernel having problems with such a big partition? (see below)
- Is the disk stuffed?

Thanks for your help.

System:
PIII 500
256 M RAM
27 GB HD
RedHat 6.1
Squid 2.3.STABLE2
Kernel 2.2.14

Output from df -k:
---
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda1              5842632   1904028   3641808  34% /
/dev/hda5             20161172   2042772  17094260  11% /cache
---

Output from df -i:
---
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/hda1             743360   70048  673312    9% /
/dev/hda5            2562240  148705 2413535    6% /cache
---

Dump of session where squid has died and the partition is fscked:
---
[root@erwin /root]# cd /usr/local/squid/logs
[root@erwin logs]# tail cache.log
2000/04/15 04:02:19| Target number of buckets: 33512
2000/04/15 04:02:19| Using 65536 Store buckets
2000/04/15 04:02:19| Max Mem  size: 32768 KB
2000/04/15 04:02:19| Max Swap size: 18432000 KB
2000/04/15 04:02:19| /cache/1/swap.state.new: (28) No space left on device
FATAL: storeDirOpenTmpSwapLog: Failed to open swap log.
Squid Cache (Version 2.3.STABLE2): Terminated abnormally.
CPU Usage: 0.030 seconds = 0.010 user + 0.020 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 261
[root@erwin logs]# cd
[root@erwin /root]# umount /cache
[root@erwin /root]# fsck /cache
Parallelizing fsck version 1.15 (18-Jul-1999)
e2fsck 1.15, 18-Jul-1999 for EXT2 FS 0.5b, 95/08/09
/dev/hda5 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -239250 -245650 -2675346 -4384146 -4384658 -4390546
Fix<y>? yes
Inode bitmap differences:  -76691 -93779 -94291 -2072659 -2168211
Fix<y>? yes
/dev/hda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda5: 144224/2562240 files (8.1% non-contiguous), 568987/5120710 blocks
[root@erwin /root]# mount /cache
[root@erwin /root]# /etc/rc.d/init.d/squid start
Starting squid: squid
---


-- 
Phil Hutton
Systems Administrator
Lincoln College, Adelaide, Australia
Phone:  +61 8 8290 6124
E-mail: philhutton@bigfoot.com

-- 
LinuxSA WWW: http://www.linuxsa.org.au/  IRC: #linuxsa on irc.linux.org.au
To unsubscribe from the LinuxSA list:
  mail linuxsa-request@linuxsa.org.au with "unsubscribe" as the subject


Index: [thread] [date] [subject] [author]
Return to the LinuxSA Mailing List Information Page