From: Matthew Wilcox <matthew@wil.cx>
To: Levy_Jerome@emc.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] scsi_dh: add ALUA notification for EMC Clariion devices
Date: Tue, 23 Sep 2008 09:57:28 -0600 [thread overview]
Message-ID: <20080923155728.GD27204@parisc-linux.org> (raw)
In-Reply-To: <6416EE16C1AF1E4C86882867E4DD0FF6026D1BF1@CORPUSMX40B.corp.emc.com>
On Tue, Sep 23, 2008 at 10:46:18AM -0400, Levy_Jerome@emc.com wrote:
> Adding sense code data decode and notification for optimal/non-optimal
> path changeover on Clariion devices. Unfortunately in the read sense
> code we can't do another inquiry, so we can't tell the user whether we
> are on the optimal or non-optimal path, only that a change has occurred.
I'm not sure that printk is the optimal user notification here.
What if we had a uevent so that udev could take action, such as issuing
an inquiry?
What if we scheduled some work so we could issue an inquiry and take
appropriate action?
> case UNIT_ATTENTION:
> + if (sense_hdr->asc == 0x2A && sense_hdr->ascq == 0x06)
> + /*
> + * ALUA status has changed. Report to host,
> + * no further action required... jml
> + */
> + sdev_printk(KERN_NOTICE, sdev,
> + "%s: Asymmetric access state has
> changed.\n",
> + CLARIION_NAME);
> + return SUCCESS;
> + break;
> if (sense_hdr->asc == 0x29 && sense_hdr->ascq == 0x00)
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-09-23 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 14:46 [PATCH 1/1] scsi_dh: add ALUA notification for EMC Clariion devices Levy_Jerome
2008-09-23 15:57 ` Matthew Wilcox [this message]
2008-09-23 16:04 ` Levy_Jerome
2008-10-13 17:41 ` [PATCH 1/1] scsi_dh: fix boot oops with EMC Clariion Levy_Jerome
2008-10-17 17:34 ` James Bottomley
2008-10-17 18:17 ` Levy_Jerome
2008-10-17 18:33 ` James Bottomley
2008-10-17 18:35 ` Levy_Jerome
2008-10-17 18:37 ` Ric Wheeler
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=20080923155728.GD27204@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Levy_Jerome@emc.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 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.