From: Ewan Milne <emilne@redhat.com>
To: James Bottomley <jbottomley@parallels.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"rwheeler@redhat.com" <rwheeler@redhat.com>,
Kirill Korotaev <dev@parallels.com>
Subject: Re: [PATCH v3 0/6] [SCSI] Enhanced sense and Unit Attention handling
Date: Mon, 22 Jul 2013 17:13:22 -0400 [thread overview]
Message-ID: <1374527602.4139.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1374507094.2335.21.camel@dabdike>
On Mon, 2013-07-22 at 15:31 +0000, James Bottomley wrote:
> Ping on this, please.
>
> I have another possible consumer of this infrastructure, when it's
> ready, which is the SCSI RAID drivers. We've been getting complaints
> that there's no event we get from them when a RAID system goes from
> online -> degraded which should be the sysadmin's cue to go in and
> replace the disk (well, this isn't quite true, a lot come with
> proprietary monitoring daemons which do this, but they're pretty unique
> per controller).
>
> I was thinking we might resurrect the orphaned raid_class.c to do this
> and give a universally displayable but rudimentary view of the topology
> and health of the device and add an easy hook for RAID events.
>
> James
>
I'm testing a v4 version of these patches, which address your earlier
comments. I'm still working on the code to suppress the duplicate
REPORTED LUNS DATA HAS CHANGED unit attentions from multiple LUNs.
As I mentioned in my earlier mail, doing this with the expected_cc_ua
mechanism is imperfect, because SCSI-3 devices will stop reporting it
when one of the LUNs on the target *receives* a REPORT LUNs command, and
it is difficult to know when this happens. I'm trying out clearing
the flag before the SCSI scan code issues a REPORT LUNs, that might be
good enough. (It doesn't handle someone from sending this command
through the sg driver, though.)
Will post the v4 soon.
-Ewan
prev parent reply other threads:[~2013-07-22 21:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 17:42 [PATCH v3 0/6] [SCSI] Enhanced sense and Unit Attention handling Ewan D. Milne
2013-06-19 17:42 ` [PATCH v3 1/6] [SCSI] Add a kernel config option for enhanced Unit Attention support Ewan D. Milne
2013-06-19 18:35 ` James Bottomley
2013-06-19 18:52 ` Ewan Milne
2013-06-19 17:42 ` [PATCH v3 2/6] [SCSI] Rename scsi_evt_xxx to sdev_evt_xxx and scsi_event to sdev_event Ewan D. Milne
2013-06-19 18:36 ` James Bottomley
2013-06-24 13:49 ` Ewan Milne
2013-06-19 17:42 ` [PATCH v3 3/6] [SCSI] Add support for scsi_target events Ewan D. Milne
2013-06-19 17:54 ` Bart Van Assche
2013-06-19 18:49 ` Ewan Milne
2013-06-19 17:42 ` [PATCH v3 4/6] [SCSI] Generate uevents for certain Unit Attention codes Ewan D. Milne
2013-06-19 18:48 ` James Bottomley
2013-06-24 14:11 ` Ewan Milne
2013-06-24 14:58 ` James Bottomley
2013-06-27 15:37 ` Ewan Milne
2013-06-20 8:35 ` Hannes Reinecke
2013-06-19 17:42 ` [PATCH v3 5/6] [SCSI] Add sysfs support for enhanced Unit Attention handling Ewan D. Milne
2013-06-19 17:42 ` [PATCH v3 6/6] [SCSI] Add sense and Unit Attention generation to scsi_debug Ewan D. Milne
2013-07-22 15:31 ` [PATCH v3 0/6] [SCSI] Enhanced sense and Unit Attention handling James Bottomley
2013-07-22 21:13 ` Ewan Milne [this message]
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=1374527602.4139.27.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=dev@parallels.com \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rwheeler@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).