Kernel Driver device file association...

[Chris Schafer]

I have and IBM tivoli driver I need to use for my changer. It loads and the tape drive one works correctly. The one associated with the library controller does not map the /dev/rmt/tsmlb0 file to the driver in the kernel.

Meaning the below returns...
ioscan -fnkC autochClass I H/W Path Driver S/W State H/W Type Description
=======================================================================
autoch 0 0/6/2/0.8.0.255.1.8.1 tsmchgr CLAIMED DEVICE HP A5597A

but no device file. So time last week this started being the case.

I am trying to switch back and forth from the IBM drivers and the HP ones and the HP ones are working and the IBM ones fail.

This is the script we use to remove the IBM drivers and start omniback.

bash-2.05b# cat omni.sh
#!/bin/sh
rmsf -H 0/6/0/0.8.0.255.1.8.0
rmsf -H 0/6/0/0.8.0.255.1.8.1
rmsf -H 0/6/2/0.8.0.255.1.8.0
rmsf -H 0/6/2/0.8.0.255.1.8.1
rmsf -H 0/6/2/0.8.0.255.1.8.2
ioscan -M stape -H 0/6/0/0.8.0.255.1.8.0
ioscan -M stape -H 0/6/0/0.8.0.255.1.8.1
ioscan -M stape -H 0/6/2/0.8.0.255.1.8.0
ioscan -M sctl -H 0/6/2/0.8.0.255.1.8.1
ioscan -M stape -H 0/6/2/0.8.0.255.1.8.2
insf -H 0/6/0/0.8.0.255.1.8
insf -H 0/6/2/0.8.0.255.1.8
/sbin/init.d/omni start
/sbin/init.d/w_registry start
bash-2.05b#

This is the script we use to put the IBM drivers in place and start TSM.

bash-2.05b# cat tsm.sh
#!/bin/sh

# start the tsm configuration

/opt/tivoli/tsm/devices/bin/tsmddcfg 0/6/0/0.8.0.255.1.8.0
/opt/tivoli/tsm/devices/bin/tsmddcfg 0/6/0/0.8.0.255.1.8.1
/opt/tivoli/tsm/devices/bin/tsmddcfg 0/6/2/0.8.0.255.1.8.0
/opt/tivoli/tsm/devices/bin/tsmddcfg 0/6/2/0.8.0.255.1.8.1
/opt/tivoli/tsm/devices/bin/tsmddcfg 0/6/2/0.8.0.255.1.8.2

/usr/sbin/ioscan -fnkC tape
/usr/sbin/ioscan -fnkC autoch

export DSMSERV_DIR=/opt/tivoli/tsm/server/bin
cd /opt/tivoli/tsm/server/bin/
cp -f /var/adm/tsmserv.log /var/adm/tsmserv.old
nohup /opt/tivoli/tsm/server/bin/dsmserv >/var/adm/tsmserv.log 2>&1 &

This is the current device out put.

bash-2.05b# ioscan -fnkC autoch
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
autoch 0 0/6/2/0.8.0.255.1.8.1 tsmchgr CLAIMED DEVICE HP A5597A

bash-2.05b# ioscan -fnkC tape
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
tape 0 0/6/0/0.8.0.255.1.8.0 tsmtape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/tsmmt0
tape 1 0/6/0/0.8.0.255.1.8.1 tsmtape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/tsmmt1
tape 2 0/6/2/0.8.0.255.1.8.0 tsmtape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/tsmmt2
tape 3 0/6/2/0.8.0.255.1.8.2 tsmtape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/tsmmt3


As far as I can tell the IBM script is building the mknod command line correctly. But for some reason it is not working.

[Jakes Louw]

I've seen this on a Plasmon changer. Some things to investigate:
1) Is the SCSI cabling as per regulation? We found we were running a 15m SCSI-LVD cable, but the documentation all mentions 10m as max. We got intermittent occurrences where the platters went "NO H/W".
2) Have you booted the changer?

[Steve Lewis]

Try to insf the tsm files and
then please post the output of

lsdev | grep -E 'autoch|schgr|tsmchgr'
ll /dev/rmt

I or someone else will help you create the device file manually using the major number of the device driver and the correct minor number for the controller.

We also need the number of the ext_bus that is above the line in ioscan.fn