From: Stefan Kaltenbrunner <mm-mailinglist@madness.at>
To: nelsonis@earthlink.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Any known issues with MPT SCSI?
Date: Thu, 11 Dec 2003 21:34:27 +0100 [thread overview]
Message-ID: <3FD8D4D3.5010609@madness.at> (raw)
In-Reply-To: <3FD73C61.80708@earthlink.net>
Ian S. Nelson wrote:
> I'm running some Dell 1750s with a moderately customized 2.4.20 kernel,
> it has a couple of newer drivers but it's fairly standard. I have 3
> identical systems that are turning up ext3 corruption fairly regularly.
> They are using the MPT/53c1030 SCSI. 2 of the 3 reported log corruption
> on a boot and mounted the root filesystem in read only. The other is
> spitting
FWIW: we have more than a dozen of IBM x335/345 maschines using this
controller (using 2.4.22 and 2.4.23), and most of these server do have
_significant_ IO-Load at times . Whe have not yet encountered anything
near a corrupted filesystem although the controllers itself do "feel"
quite slow.
Stefan
prev parent reply other threads:[~2003-12-11 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 15:31 Any known issues with MPT SCSI? Ian S. Nelson
2003-12-11 20:34 ` Stefan Kaltenbrunner [this message]
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=3FD8D4D3.5010609@madness.at \
--to=mm-mailinglist@madness.at \
--cc=linux-kernel@vger.kernel.org \
--cc=nelsonis@earthlink.net \
/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