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: Thu, 2 Aug 2001 14:26:31 -0700 [thread overview]
Message-ID: <20010802142631.A25795@vger.timpanogas.org> (raw)
In-Reply-To: <20010801185836.B22548@vger.timpanogas.org> <E15SHUV-0000SM-00@the-village.bc.nu>
In-Reply-To: <E15SHUV-0000SM-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Aug 02, 2001 at 01:22:15PM +0100
On Thu, Aug 02, 2001 at 01:22:15PM +0100, Alan Cox wrote:
> > 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.
>
> Looks fine to me. However if you are seeing 0 block length drives reported
> thats tw_scsiop_read_capacity_complete() causing the sd.c code to do
> something daft.
>
> Alan
Alan,
Thanks. I will look at this. I am running into this problem on 2.2.X
kernels more so than 2.4.X, but occasionally see it on 2.4.X. It seems
related to RAID recovery during testing. We noticed it when we were
triggering RAID failover for testing.
Jeff
next prev parent reply other threads:[~2001-08-02 20:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 18:14 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
2001-08-02 12:22 ` Alan Cox
2001-08-02 21:26 ` Jeff V. Merkey [this message]
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=20010802142631.A25795@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
all inboxes | Powered by JetHome®