WRITE EXTENDED is WRITE(10), I believe. The ECC-writing version is
WRITE LONG; IBM (at least) implements it.
At 11:47 AM -0600 2001-07-15, Justin T. Gibbs wrote:
>As the soft reset section also specifies how to deal with initiators
>that are not expecting soft reset semantics, I believe this applies to
>either reset model.
>If we look at the section on caching for direct access devices we see,
>"[write-back cached] data may be lost if power to the device is lost or
>a hardware failure occurs". There is no mention of a bus reset having
>any effect on commands already acked as completed to the intiator.
I'd very much like to think so; thanks for the reference. I'd feel a
little more sanguine about the subject if there were some explicit
guarantee of the desired behavior, either in the SCSI spec or in an
implementer's functional spec. Nonetheless, it's testable behavior,
and it's a reasonable inference that drives should behave correctly.
-- /Jonathan Lundell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/