lkml.org 
[lkml]   [2000]   [Oct]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Corruption on database
Date
From
> We have problems with the database under high I/O load. The kernel doesn't
> report any hardware error (sync problems or the like) but the database often

It generally won't. PC's dont come with any kind of decent hardware error
checking in general. If you have ECC memory Dan Hollis has a daemon for
monitoring it, for non ECC memory things like memtest86 can help

> Used is kernel 2.2.16-22SAPenterprise, a 'special' kernel from Redhat with
> some patches (Bigmem, semaphores, LFS etc.).

You probably want to take this to a Red Hat list and Red Hat Bugzilla since
the extra stuff makes it tricky for folks working on a standard kernel to
look into. Also after the signal 11 check dmesg for an 'oops' entry.

> than 2 GB and their behaviour under high/very high load. Due to the fact,
> that we have this problem on two nearly identical machines I assume that
> there's no hardware problem with the controller.

Ok that is good evidence.

Can you put this in bugzilla.redhat.com/bugzilla and it'll go in the right
direction


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:39    [W:0.037 / U:1.232 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site