Re: [Ips] iSCSI-specific unit attention conditions

Paul Koning <> Tue, 31 March 2009 19:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BCF763A6899 for <>; Tue, 31 Mar 2009 12:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -104.054
X-Spam-Status: No, score=-104.054 tagged_above=-999 required=5 tests=[AWL=-0.151, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_RELAY=2.696, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BSX-qEMtQthX for <>; Tue, 31 Mar 2009 12:31:33 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id C5D153A6817 for <>; Tue, 31 Mar 2009 12:31:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.39,303,1235973600"; d="scan'208";a="392934856"
Received: from unknown (HELO ([]) by with SMTP; 31 Mar 2009 14:32:31 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18898.28621.87089.387064@gargle.gargle.HOWL>
Date: Tue, 31 Mar 2009 15:32:29 -0400
From: Paul Koning <>
References: <18898.26477.64898.577194@gargle.gargle.HOWL> <>
X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid
X-OriginalArrivalTime: 31 Mar 2009 19:32:30.0272 (UTC) FILETIME=[6E729C00:01C9B237]
Subject: Re: [Ips] iSCSI-specific unit attention conditions
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 31 Mar 2009 19:31:33 -0000

>>>>> "Frederick" == Frederick Knight <Knight> writes:

 Frederick> My interpretation of the "update" part of the agenda was
 Frederick> that SAM-4 was an example (and that we should also include
 Frederick> SAM-3 and SAM-5 as part of the update list).  Therefore,
 Frederick> to add SPC to the update list is (in my opinion) within
 Frederick> the scope for the SCSI Update portion of this project.

 Frederick> Yes, it should be included in the charter (either
 Frederick> specifically, or by making clear the broader
 Frederick> interpretation of the "update").

Ok, that sounds good.

 Frederick> There is no person advocating these ASC/Q codes.  These
 Frederick> are ALREADY APPROVED ASC/Q codes, and the person that
 Frederick> caused them to become approved is no longer part of T10,
 Frederick> nor is that company a part of T10 at this time, so it will
 Frederick> be hard to find them and get them to do anything.

 Frederick> In my opinion, we should define their use, and let the
 Frederick> e-mail reviews make sure we get it right (or as good as we
 Frederick> can).  Partly because, contrary to the statement below,
 Frederick> the causes of all unit attention conditions are not
 Frederick> "clearly defined".

I was assuming the person doing the advocating would be the
appropriate one to do the defining.  If that person isn't around but
someone else wants to do the defining, that is fine, too.

Part of what bothers me is that I can't fathom what these codes are
intended for, or what the scenarios are when they might be generated,
or what conclusion an initiator is supposed to draw when it sees one.

The names vaguely suggest that they have something to do with
asynchronous logout, but that is already fully covered in the iSCSI
spec.  Itdoesn't require any unit attentions in the first place,
certainly not any iSCSI specific ones.

I would rather see these things go away, unless there is a good
argument made that there is something missing in iSCSI that needs to
be added, and these codes are part of the solution.  The fact that T10
already approved them isn't a reason to add them to iSCSI.