XCopy and failure status

Knight, Frederick Frederick.Knight at netapp.com
Wed Nov 28 04:30:57 PST 2012


Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1211283_f.htm">HTML-formatted message</a>

See (SPC4r36e, page 263):
5.17.7.4 EXTENDED COPY command errors detected during processing of segment
descriptors
<...>
d) if the exception condition is reported by the copy source, then:
<...>
e) if the exception condition is reported by the copy destination, then:
There are pointers setup either in the first/second byte of the
COMMAND-SPECIFIC INFORMATION field (first byte = source device, second byte =
destination device); or the forwarded additional sense data descriptor is
used (depending on whether you're returning fixed or descriptor format sense
data.
		Fred
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Kevin D Butt
Sent: Tuesday, November 27, 2012 5:56 PM
To: T10 Reflector
Subject: XCopy and failure status
When performing an extended copy and a failure occurs how does one determine
which device, the source CSCD or the destination CSCD, generated the sense
data related to the failure?
I can see how to discover which operation caused the failure, but I would
think the Parameter data for the RECEIVE COPY FAILURE DETAILS(LID1)command
should contain a pointer to the CSCD which generated the sense data.  The
same for the Parameter data for the RECEIVE COPY STATUS(LIDx) commands.
Thanks,
Kevin D. Butt
SCSI & Fibre Channel Architect, Tape Firmware
Data Protection & Retention
MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
Tel: 520-799-5280
Fax: 520-799-2723 (T/L:321)
Email address: kdbutt at us.ibm.com
http://www-03.ibm.com/servers/storage/



More information about the T10 mailing list