On Thu, 19 Sep 2002, Paul Weber wrote:
> Sorry for the delay, we had a server go down.
>
> Somewhere in the last few messages, the things I tried must have shaken
> something loose. Now, the tape drive shows up in /proc/scsi/scsi, and
> the device /dev/st0 exists. I now hold in my hot little hands the first
> tape backup of this system. (It was a different one that went down,
> BTW.)
>
> Now comes the real worry. It works, but I don't know why.
>
> If you have any insights as to what might have changed, let me know.
> The initial problem seems to have been that the aic7xxx module didn't
> load. After loading it manually, the st module loaded and the rest of
> the stuff appeared. Now it seems to be loading itself. I'd really like
> to know why it wasn't loading before and why it's loading now. What
> controls the loading of modules?
>
I can't tell you what changed, but so far as what controls the loading
of scsi tape modules is concerned, during boot, execution of
/etc/rc.d/rc.sysinit does the following:
# If a SCSI tape has been detected, load the st module unconditionally
# since many SCSI tapes don't deal well with st being loaded and unloaded
if [ -f /proc/scsi/scsi ] && grep -q 'Type: Sequential-Access'
/proc/scsi/scsi 2>/dev/null ; then
if grep -qv ' 9 st' /proc/devices ; then
if [ -n "$USEMODULES" ] ; then
# Try to load the module. If it fails, ignore it...
insmod -p st >/dev/null 2>&1 && modprobe st >/dev/null 2>&1
fi
fi
fi
--
Steven Yellin
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
