![]() | |||||||||||||
Messages in this thread |
> > I'm not sure how far along the chain you have to go in the scsi subsystem
> > before the bits trip to say that the module is in use, but at this point
> > I can only presume it wasn't far enough.
>
> Cool idea. Maybe we could have an option in the config file which could
> specify a different wait time for different modules so people with slow
> devices could set the timeout on those modules to 2 minutes, for instance.
and increase the timeout for some other modules !
once I had a machine with a dedicated SCSI controller (aha152x) for an external
SCSI tape drive. thus the aha152x driver got unloaded whenever you left
the tape idle a little while and the re-loading caused a SCSI bus reset
which rewound the tape :-(
this is *very* nasty if you're trying to read/write multiple archives etc...
the only chance right now is to increase timeout for all modules (used 2h)
or to load those modules myself...
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^
| ||||||||||||
| Last update: 2005-03-22 12:38 [W:0.055 / U:0.020 seconds] ©2003-2008 Jasper Spaans | |||||||||||||