From: Gaute Lund <gaute@idrift.no>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Random file system errors
Date: Sun, 07 Jun 2009 13:44:32 +0200 [thread overview]
Message-ID: <34798D56CB2CB9B45352017A@LEYLA> (raw)
In-Reply-To: <20090429061910.348CD31402A@mail.idrift.no>
Thanks again Clyde, Geoff and f-lvm@media.mit.edu and others who gave
advice. Turns out it was a RAM issue.
Just to close off this threadm, even if it's old. This is "only" a
private/testing box, and I've been busy, so I've only been able to test
stuff every now and then.
A few runs of memtest86 found no errors. I turned to the "md5sums of parts
of disks" approach. If I read large chunks (5 GB), from different places on
the disks, with 5+ iterations with each chunk, I got errors occasionally
(diverging md5sums). But this is 10 disks across two controllers and all
but two gave errors several times, albeit seldomly.
I started swapping hardware, and with different RAM I am OK. I guess clean
runs of memtest shouldn't be trusted 100%. I can even say, the way these
errors have crept up on me gradually over months(!), it means the RAM
stick(s) have failed gradually, without being touched or anything. Scary!
-gaute
--On 29. April 2009 08:19 +0200 Gaute Lund <gaute@idrift.no> wrote:
> Thanks, and also to others who gave feedback. The approach with
> md5summing devices came from another source too, and I'll try a
> systematic approach as soon as time allows.
next prev parent reply other threads:[~2009-06-07 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 6:19 [linux-lvm] Random file system errors Gaute Lund
2009-06-07 11:44 ` Gaute Lund [this message]
2009-06-07 15:16 ` Clyde E. Kunkel
-- strict thread matches above, loose matches on Subject: below --
2009-04-28 1:52 Gaute Lund
2009-04-28 3:32 ` f-lvm
2009-04-28 3:50 ` Steer, Geoff
2009-04-28 14:41 ` Clyde E. Kunkel
2009-04-28 17:00 ` Greg Freemyer
2009-04-29 3:52 ` f-lvm
2009-04-29 19:02 ` Clyde E. Kunkel
2009-04-30 23:33 ` Clyde E. Kunkel
2009-05-01 1:28 ` f-lvm
2009-04-30 16:17 ` Philipp Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34798D56CB2CB9B45352017A@LEYLA \
--to=gaute@idrift.no \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.