Steve,
Could you confirm whether, in your environment, the scsi_debug
driver has the same problem.
Doug Gilbert
Stephen Cameron wrote:
--- On Fri, 1/15/10, Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx> wrote:
...
Did you check that also after, say, several minutes?
I suppose you
already looked at the kernel log for possibly related
messages and would
have reported them as well... Nevertheless, I have
seen some cases of
device removal or driver removal where the SCSI layer spent
many minutes
(5? 15? I'm not sure anymore) in error handling although
the lower layer
had done its best (best but perhaps not well) to report the
device as
physically gone.
Did you already test really long after device removal and
last close,
along the lines of this?
# while ((i++ < 20)); do rmmod $driver && break;
sleep 60; done
I had left it sitting since last night (~6:00pm localtime), and this morning (~8:00am localtime), it still won't rmmod... so ~14 hours.
-- steve
--
Stefan Richter
-=====-==-=- ---= -====
http://arcgraph.de/sr/
--
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
--
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
