From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Scott Ransom <ransom@cfa.harvard.edu>, linux-kernel@vger.kernel.org
Subject: Re: 3ware Escalade problems
Date: Wed, 1 Aug 2001 18:58:36 -0700 [thread overview]
Message-ID: <20010801185836.B22548@vger.timpanogas.org> (raw)
In-Reply-To: <20010801184032.A22548@vger.timpanogas.org> <E15S6Xn-00088F-00@the-village.bc.nu>
In-Reply-To: <E15S6Xn-00088F-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Aug 02, 2001 at 01:40:55AM +0100
On Thu, Aug 02, 2001 at 01:40:55AM +0100, Alan Cox wrote:
> > Try putting four adapters into a system all at once with 32 drives, and
> > you will see all sorts of bugs. I do not see problems with a single board,
> > other than gendisk reporting junk. If it's the scsi layer, then the driver
> > must not be calling the sd driver. I will attempt to get on the phone with
> > Adam, and get these issues resolved.
>
> The scsi disk layer does the entire gendisk stuff itself. Its actually
> very hard for a scsi driver to screw that up - the scsi driver has no
> real concept of a 'disk'. sd talks to a disk and the scsi driver just gets
> messages posted around.
>
> Alan
Alan,
If you have an adapter, install it, dumop and gendisk head, and take a
look at what's happening. I am seeing drives being reported with 0
block lengths and other wierdness.
Jeff
next prev parent reply other threads:[~2001-08-02 0:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 18:14 3ware Escalade problems Scott Ransom
2001-08-01 21:39 ` Jeff V. Merkey
2001-08-02 0:26 ` Alan Cox
2001-08-02 1:40 ` Jeff V. Merkey
2001-08-02 0:40 ` Alan Cox
2001-08-02 1:58 ` Jeff V. Merkey [this message]
2001-08-02 12:22 ` Alan Cox
2001-08-02 21:26 ` Jeff V. Merkey
2001-08-02 22:02 ` Jeff V. Merkey
2001-08-02 14:19 ` 3ware Escalade problems? Adaptec? Michael Rothwell
[not found] <53B208BD9A7FD311881A009027B6BBFB9EADC7@siamese>
2001-08-01 18:51 ` 3ware Escalade problems Scott Ransom
[not found] <53B208BD9A7FD311881A009027B6BBFB9EADCC@siamese>
2001-08-02 1:38 ` Jeff V. Merkey
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=20010801185836.B22548@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ransom@cfa.harvard.edu \
/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