Linux Kernel Panic

From: Jan Van Ham <Responsible@dont-contact.us>
Date: Tue, 21 Dec 1999 09:32:24 +0100

Hi again,

Sorry my question has little to do with Squid, but since I don't understand this problem :

- I've a Squid 2.2.STABLE5 on kernel 2.2.13
- I've added some extra RAM to my system...
- It ran fine for a few minutes (waauuw...what an uptime) and then kernel panic : Free list corrupted

=> Is it OK to created a volume with 1 000 000 i-node entries ??? (does this eat additional diskspace ?)

- Even AFTER removing the "faulty" memory and putting the old SIMMS back into place ... again the same kernel panic!?!

How is this possible ? I'm going to make my production cache soon ... but I don't want THIS to happen ;-))

Some screen output :

Parallelizing fsck version 1.14 (9-Jan-1999)
/dev/hda1: clean , 74821/366592 files , 891539/1461568 blocks
/dev/hdb1 was not cleanly unmounted , check forced
/dev/hdc1 was not cleanly unmounted , check forced
Kernel panic: Free list corrupted

Should I take care of special parameters when running "mkfs.ext2" to create my cache-filesystems ??
I do only mkfs.ext2 -N 1000000 /dev/hdc1
               mkfs.ext2 -N 1000000 /dev/hdb1

Any ideas ?
Jan
Received on Tue Dec 21 1999 - 01:40:52 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:50:03 MST