We are seriously in trouble if the subsystems above us don't know how
to deal with dead targets. We are encountering scenarios in which the
data structures are staying around due to references, but for all other
intents they're gone. I know that DM has yet to fully account for this.
md - it's dead. Applications... they have no clue.
I think we should seriously reconsider this position. FC is the only major
storage transport that does this (USB doesn't count). Parallel SCSI
doesn't, iSCSI doesn't, SAS doesn't. If the device was truly gone, ok.
But, if we expect the device to come alive again sometime in the future,
why not keep the tree in place ?
-- james s
Christoph Hellwig wrote:
On Mon, Jun 12, 2006 at 06:16:42PM -0500, Michael Reed wrote:
If the fc transport removes the scsi infrastructure for a
disconnected target and that target subsequently returns,
those subsystems layered upon scsi which don't understand
the implications of this disconnection / reconnection may
be unable to access the reconnected scsi target. This patch
makes the target removal configurable.
NACK, we don't want to keep dead targets around.
-
: 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
