public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Hejtmanek <xhejtman@mail.muni.cz>
To: Joshua Schmidlkofer <kernel@pacrimopen.com>
Cc: Samuel Flory <sflory@rackable.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux@3ware.com
Subject: Re: 3ware driver broken with 2.4.22/23 ?
Date: Tue, 30 Dec 2003 00:49:02 +0100	[thread overview]
Message-ID: <20031229234902.GL916@mail.muni.cz> (raw)
In-Reply-To: <1072503925.27022.222.camel@menion.home>

On Fri, Dec 26, 2003 at 09:45:25PM -0800, Joshua Schmidlkofer wrote:
> 
> >    Generally not with such a small rev difference.  You could try the 
> > latest driver, and firmware in the 7.7.  The driver source is on the Red 
> > Hat drivers disk.  You should be able to drop in the .c, and .h in 
> > drivers/scsi, and recompile.
> > http://3ware.com/support/download.asp?code=5&id=7.7.0&softtype=Driver&releasenotes=&os=Windows
> > 
> > PS- Personally I'd suspect an XFS bug.  Try reiserfs.  I've been running 
> > 2.4.23pres, and 2.4.23 on hundreds of 3ware of numerous different types. 
> >   With no issue with the prior firmware release.
> 
> There are a lot of people, running RAID5 3ware's w/ Terrabyte arrays.  I
> don't want to say it is not an XFS bug, but I find that highly suspect. 

Well, with ext3 parition iozone program finishes OK. So it looks like some XFS
bug.

-- 
Lukáš Hejtmánek

  reply	other threads:[~2003-12-29 23:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21 11:21 3ware driver broken with 2.4.22/23 ? Lukas Hejtmanek
2003-12-21 11:29 ` Martin Loschwitz
2003-12-21 11:48 ` Andre Tomt
2003-12-22  1:16 ` Samuel Flory
2003-12-27  5:45   ` Joshua Schmidlkofer
2003-12-29 23:49     ` Lukas Hejtmanek [this message]
2003-12-29 23:59       ` Joshua Schmidlkofer

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=20031229234902.GL916@mail.muni.cz \
    --to=xhejtman@mail.muni.cz \
    --cc=kernel@pacrimopen.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@3ware.com \
    --cc=sflory@rackable.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox