Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Stephen Samuel (darkoncgmail.com)
Date: Mon Sep 17 2007 - 14:59:11 CDT
You may want to excercise your I/O subsystem.
Given that you probably don't want to stomp on a live filesystem, you
might want to create a file of a couple of gigabytes and turn it into
a pseudo-device with
# make a 15GB test file
dd if=/dev/zero of=the_testfile bs=1M count=15000
# find a free loopback pseudo-device
# attach it to the 5GB test file
losetup $device the_testfile
# exercise this block of data
nice badblocks -w -p5 $device # 5 passes of a read-write test.
The other thing to do would be a memory test, to makes sure that
there's not something very wrong with your memory subsystem. I think
that there are tools that can do a *partial* memtest on a live system,
but a (really) quick look didn't find them.
Most distributions have a memtest boot option which runs a
(reasonably) complete memory test.
On 9/17/07, Andreas Dilger <adilgerclusterfs.com> wrote:
> On Sep 17, 2007 13:31 -0400, Maurice Volaski wrote:
> > In using drbd 8.0.5 recently, I have come across at least two
> > instances where a bit on disk apparently flipped spontaneously in the
> > ext3 metadata on volumes running on top of drbd.
> > Also, I have been seeing regular corruption of a mysql database,
> > which runs on top of drbd, and when I reported this as a bug since I
> > also recently upgraded mysql versions, they question whether drbd
> > could be responsible!
> Seems unlikely - more likely to be RAM or similar (would include cable
> for PATA/SCSI but that is less likely an issue for SATA).
> Cheers, Andreas
> Andreas Dilger
> Principal Software Engineer
> Cluster File Systems, Inc.
> Ext3-users mailing list
Stephen Samuel http://www.bcgreen.com
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql