From: Samuel Flory <sflory@rackable.com>
To: "martin.knoblauch " <"martin.knoblauch "@mscsoftware.com>
Cc: gibbs@scsiguy.com, linux-kernel@vger.kernel.org
Subject: Re: File system corruption under 2.4.21-pre5-ac1
Date: Tue, 01 Apr 2003 12:23:11 -0800 [thread overview]
Message-ID: <3E89F52F.3090802@rackable.com> (raw)
In-Reply-To: 3E8951D0.5327C7FE@mscsoftware.com
Martin Knoblauch wrote:
>>Re: File system corruption under 2.4.21-pre5-ac1
>>
>>From: Justin T. Gibbs (gibbs@scsiguy.com)
>>Date: Mon Mar 31 2003 - 14:26:27 EST
>>
>>
>>
>>
>>>I'm seeing filesystem corruption on a number of intel SE7501wv2's under
>>>2.4.21-pre5-ac1. The systems are running Cerberus (ctcs). They fail the
>>>kcompile, and memtst tests.
>>>
>>>
>>Are you running the aic79xx driver version embedded in that kernel version
>>or the latest from my site?
>>
>>http://people.FreeBSD.org/~gibbs/linux/SRC/
>>
>>
>>
>Justin,
>
> would you call the 1.3.6 version of aic79xx stable or "production
>quality"? There still seems to be quite a lot of changes going on.
>
>
>
Up until this point I've found the aic79xx driver to be very stable.
I know people running 100s of systems without issue on older revs of
the driver.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-04-01 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 8:46 File system corruption under 2.4.21-pre5-ac1 Martin Knoblauch
2003-04-01 20:23 ` Samuel Flory [this message]
2003-04-02 7:14 ` Martin.Knoblauch
2003-04-02 0:44 ` Justin T. Gibbs
-- strict thread matches above, loose matches on Subject: below --
2003-04-01 1:25 Samuel Flory
2003-03-31 19:26 ` Justin T. Gibbs
2003-04-01 18:11 ` Samuel Flory
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=3E89F52F.3090802@rackable.com \
--to=sflory@rackable.com \
--cc="martin.knoblauch "@mscsoftware.com \
--cc=gibbs@scsiguy.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 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.