Sachin Sant wrote:
Does Current sg driver offer SCSI reserve/release command in its
open/close function.
No.
I am trying to run on a SAN or Cluster environment
which requires support for this reserve/release command.
BTW www.t10.org traffic suggests more sophisticated reserve/
release mechanisms are in the pipeline. IOWs a solution to
your problem now could be an impediment a few years down the
track.
If not then are there any plans to support reserve/release SCSI command
so that sg driver can provide these options for its users in its
open/close function It will make all I/O operation with sg driver more
reliable especially in data storage area.
I'm getting this request from several angles. As someone
wryly pointed out ... as if we haven't got enough trouble
at the moment with the scsi subsystem implicitly issuing
scsi commands :-)
Seriously, I don't think issuing reserve/release SCSI commands
on the open and close of a pass-through interface is a good
idea. At a stretch it could be a non-default parameter on the
sg driver [lk 2.4 via /proc/scsi/sg; in lk 2.6 ...]
Just thinking about the implementation: currently sg will hold
its data structures alive if an unexpected close (e.g. user
control-C) occurs while a SCSI command is in flight. I guess
the point of what you are suggesting is to issue another scsi
command (i.e. release) in such a situation (and wait for
it (potentially as well as a command in progress)).
Doug Gilbert
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
| 