All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Luben Tuikov <tluben@rogers.com>
Cc: Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: Patch:  allow devices to restrict start on add
Date: Sun, 25 May 2003 20:00:40 +1000	[thread overview]
Message-ID: <3ED09448.9070305@torque.net> (raw)
In-Reply-To: <3ECEE042.60208@rogers.com>

Luben Tuikov wrote:
> Eddie Williams wrote:
> 
>>
>> Sense_Key=2 Not Ready
>> ASC: 0x04, ASQ: 0x02 Logical Unit Not Ready, Initializing Command 
>> Required
> 
> 
> Thanks Eddie.
> 
> Has anyone seen this condition for locally attached (same host)
> (block) devices?  Or is it only generated by the multipathing 
> soft/hardware.

Luben,
That ASC/ASQ sequence is precisely what I see after
I spin down a Fujitsu MAM3184 (ditto for a Seagate
ST318451). The disk below is directly attached with a
single initiator. The 'sg_start 0 /dev/sg3' command spins
down the second Fujitsu disk:

# lsscsi -g
[0:0:1:0]    disk    FUJITSU  MAM3184MP        0106  /dev/sda  /dev/sg0
[1:0:3:0]    disk    FUJITSU  MAM3184MP        0105  /dev/sdb  /dev/sg3
[2:0:0:0]    cd      ATAPI    CD-RW 48X16      A.RZ  -         /dev/sg1
[3:0:0:0]    cd      CREATIVE CD5233E          1.00  -         /dev/sg2
#
# sg_dd if=/dev/sg3 of=. bs=512 count=1
1+0 records in
1+0 records out
#
# sg_start 0 /dev/sg3
#
# sg_dd if=/dev/sg3 of=. bs=512 count=1
reading: scsi status: Check Condition
Current, Sense key: Not Ready
[valid=0] Info fld=0x0, Additional sense: Logical unit not ready, 
initializing cmd. required
Raw sense data (in hex):
   70 00 02 00 00 00 00 28 00 00 00 00 04 02 00 00 00 00 03 28 00 01 05 03
   00 00 00 00 00 00 00 00
plus...: Driver_status=0x08 (DRIVER_SENSE,SUGGEST_OK)
sg_read failed, skip=0
Some error occurred,  remaining block count=1
0+0 records in
0+0 records out

So ASC,ASQ=0x4,0x2 is the normal response for recent disks
when they are sent commands (typically other than INQUIRY)
when they are spun down.

> What I'd like to know is if this condition plus another (which I'm about
> to investigate) will give a pretty consistent rule for multipathed
> devices.

Doug Gilbert



  reply	other threads:[~2003-05-25  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 15:40 Patch: allow devices to restrict start on add Eddie Williams
2003-05-22 18:05 ` Patrick Mansfield
2003-05-22 20:10   ` Eddie Williams
2003-05-23 15:00     ` Eddie Williams
2003-05-22 18:30 ` Luben Tuikov
2003-05-22 20:36   ` Eddie Williams
2003-05-24  3:00     ` Luben Tuikov
2003-05-25 10:00       ` Douglas Gilbert [this message]
2003-05-25 17:13         ` Luben Tuikov

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=3ED09448.9070305@torque.net \
    --to=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tluben@rogers.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 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.