From: Manfred Wassmann <tux.wassmann@googlemail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Spurious Filesystem corruption with ext3 + large (<400GB) hw RAID partition + SMP
Date: Fri, 6 Feb 2009 19:08:33 +0100 [thread overview]
Message-ID: <6bd94bae0902061008n251d6bb9g9b9ec5bc791dc9ae@mail.gmail.com> (raw)
In-Reply-To: <20090201014453.GC22841@khazad-dum.debian.net>
On 2/1/09, Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
[...]
> Search the list archives, there are other problem reports for that
> 3ware card, you probably want to check those.
Thank you very much, I checked these but I could not find much about
filesystem corruption problems. The most similar problem was mentioned
in http://lkml.org/lkml/2008/6/23/230 but was related to xen which
isn't in use here.
Regarding the memory test, memtest86+ ran for almost 70 hours without
detecting any error.
I trying to reproduce the problem using my installation disk and
running stress/dbench but wasn't able to do so. The only reliable way
to reproduce it is to install Ubuntu, which isn't very helpful :-(
As already said I'm no longer using ext3 for the systems in question,
so if switching filesystems really does solve my problem, this will be
my last post in this regard. In any case thanks for your help.
regards Manfred
--
Unix "Birthday" on 2009-02-13 23:31:30 UTC
...it's 1234567890 seconds since the epoch.
next prev parent reply other threads:[~2009-02-06 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 13:36 Manfred Wassmann
2009-01-31 13:46 ` Henrique de Moraes Holschuh
[not found] ` <6bd94bae0901310604u6ed876f1n77b7e2561f479ad1@mail.gmail.com>
2009-01-31 14:51 ` Manfred Wassmann
2009-02-01 1:44 ` Henrique de Moraes Holschuh
2009-02-06 18:08 ` Manfred Wassmann [this message]
2009-02-06 18:50 ` Ray Lee
2009-02-14 13:57 ` Manfred Wassmann
[not found] ` <1233415163.28790.1297773583@webmail.messagingengine.com>
2009-01-31 17:26 ` Manfred Wassmann
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=6bd94bae0902061008n251d6bb9g9b9ec5bc791dc9ae@mail.gmail.com \
--to=tux.wassmann@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®