Re: Kernel Panic

[Ben Clewett <B.Clewett@roadrunner.uk.com>]

The filesystem are ext2 and ex3:

Filesystem    Type   1M-blocks      Used Available Use% Mounted on
/dev/hda3     ext3       37038      1860     33296   6% /
/dev/hdc1     ext3        1969       119      1750   7% /apache
/dev/hda1     ext2          30         6        23  19% /boot
/dev/hdc3     ext2       37560       279     35373   1% /var/spool/mail
/dev/hdc4     ext2       35087        76     33229   1% /home


The kernel panic mensions journal.o so I guess this must be an ext3 
partision?  Probably on the '/' as no files in the 'apache' are ever 
effected.

I am not sure about the hardware, it's not easy to check, but I belive 
my /dev/hda is a 40Gb someting purchaced a year back.  On IDE.  Either a 
Seagate, a Fujisu or a Western Digital.   (Can't get cover off as 
rack-mounted and rack screwed into removable cover :)

I hope you can help me, as the implications of an old kernel or an old 
disk have radically different fix's :)

Ben

Jamie Harris wrote:
> Sounds to me like you have bad sectors on your harddisk that the
> journalling file system is trying to work around.  What file system are
> you using and what hardware?
> 
> cheers
> 
> Jamie...
> 
> 
>>Dear Linux Admin,
>>
>>On Linux 2.4 I have had three Kernel Panics recently.
>>
>>They include the following: journal.o "( ret != 0 )".  I see in the
>>source code that there is an assertion: J_ASSERT(ret != 0) in the
>>function:
>>
>>unsigned long journal_bmap(journal_t *journal, unsigned long blocknr)
>>
>>Which looks like a possible place for the origin of this.
>>
>>There is also a large amount of Hex data, which I do not have, unless
>>logged somewhere on my system unknown to me.  (I don't get many Panics,
>>not sure where panic data is logged...)
>>
>>On reboot I loose files.  Although nothing serious yet.
>>
>>The system is a POP3 server, handling about 1,000 email files and about
>>10,000 email's a day, so there is constantly great disk load by sendmail
>> and the default redhat POP3.
>>
>>Should I upgrade my kernel, or may I be doing something specific to
>>cause this?
>>
>>Thanks with any help,
>>
>>Ben Clewett.
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-admin"
>>in the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
>