Background operations and power loss expected
gerry.houlder at seagate.com
Wed Oct 5 11:15:16 PDT 2011
Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1110051_f.htm">HTML-formatted message</a>
We tend to think of the device self-test that is kicked off via a SEND
DIAGNOSTIC command to be a host initiated background task, whereas most
other background tasks (e.g., background medium scan) are device initiated.
I think this accounts for the conflict.
Perhaps SAM-5 should change wording to "Target device initiated background
operations shall not be aborted ...". I think the SEND DIAGNOSTIC command
case is the only host initiated background operation that is defined in
On Wed, Oct 5, 2011 at 12:14 PM, Truong Nguyen - SISA <
tru.nguyen at sisa.samsung.com> wrote:
> In 10-144r3 (SPC:4 Self-test and SEND DIAGNOSTIC command clean-up), text
> was added to the Self-test operations Background mode model clause,
> specifying changes regarding power loss expected handling. Specifically, in
> sub-clause 188.8.131.52 Background mode (SPC-4r32), the following text was
> "A SCSI target device shall abort a self-test being performed in the
> background mode as the result of a power loss expected event (see SAM-4)."
> However, in SAM-4r14 (and in SAM-5r07), the following text is present in
> sub-clause 5.5 Command lifetime:
> "Background operations shall not be aborted by I_T nexus loss or power
> loss expected."
> When a power loss expected event occurs, which is the correct behaviour in
> terms of the background self-test? Should it be aborted or not be aborted?
> Truong Nguyen
> Samsung Information Systems
More information about the T10