From: Patrick Mansfield <patmans@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>,
linux-scsi@vger.kernel.org
Subject: Re: Fibre Channel related crash
Date: Wed, 22 Jun 2005 10:28:32 -0700 [thread overview]
Message-ID: <20050622172832.GA11128@us.ibm.com> (raw)
In-Reply-To: <1119361784.24150.47.camel@nalwalovaton>
You should really run with a stock kernel before reporting problems to
these lists.
cc-ing linux-scsi, maybe someone there will give you more info about the
HSV110.
On Tue, Jun 21, 2005 at 08:49:44AM -0500, William Alberto Lovaton Tovar wrote:
> Jun 20 13:35:01 dnccor50 kernel: Vendor: COMPAQ Model: HSV110 (C)COMPAQ Rev: 2001
> Jun 20 13:35:01 dnccor50 kernel: Type: Direct-Access ANSI SCSI revision: 02
> Jun 20 13:35:01 dnccor50 kernel: qla2300 0000:07:03.0: scsi(0:0:1:2): Enabled tagged queuing, queue depth 32.
> Jun 20 13:35:01 dnccor50 kernel: SCSI device sdb: 167772160 512-byte hdwr sectors (85899 MB)
> Jun 20 13:35:01 dnccor50 kernel: sdb: asking for cache data failed
> Jun 20 13:35:01 dnccor50 kernel: sdb: assuming drive cache: write through
> Jun 20 13:35:01 dnccor50 kernel: SCSI device sdb: 167772160 512-byte hdwr sectors (85899 MB)
> Jun 20 13:35:01 dnccor50 kernel: sdb: asking for cache data failed
> Jun 20 13:35:01 dnccor50 kernel: sdb: assuming drive cache: write through
> Jun 20 13:35:01 dnccor50 kernel: sdb:<6>Device sdb not ready.
> Jun 20 13:35:01 dnccor50 kernel: end_request: I/O error, dev sdb, sector 0
It isn't a fibre channel crash.
The device is (obviously) not ready. Usually, sd during probe spins up the
device, but the HSV110 is special cased, so we don't spin it up (send a
START STOP command), and it just keeps telling us it is still not ready.
Since it's a disk array, I don't know what a START / spinup means for it,
or why it is not ready. I would guess it has some sort of failure and is
waiting for you to fix it :)
You should check the device: verify its settings, check for failures,
and/or reset it; or maybe send it a START UNIT to the device.
You can try to dynamically modify the scsi_devinfo/bflags so it sends the
START STOP during probe:
change the devinfo list (won't be reset to the original until you reload
scsi_mod), I don't know if I have this exactly right:
echo "COMPAQ :HSV110 (C)COMPAQ:0x0" > /proc/scsi/device_info
remove and re-scan for the device
echo 1 > /sys/block/sd/device/delete
echo "0 1 2" > /sys/class/scsi_host/host0/scan
And see what happens ... you should see some "spinning up disk ..."
messages.
-- Patrick Mansfield
next parent reply other threads:[~2005-06-22 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1119361784.24150.47.camel@nalwalovaton>
2005-06-22 17:28 ` Patrick Mansfield [this message]
2005-06-23 13:52 ` [dm-devel] Fibre Channel related crash Philip R Auld
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=20050622172832.GA11128@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox