- Joined
- Apr 2, 2007
- Messages
- 617
- Reaction score
- 72
- Points
- 0
- Location
- Oslo, Norway
- Website
- www.basefarm.no
My expirience with TSM 5.4.0.3 that may be useful for other people.
Hardware:
IBM x226 (3 GHz and 3 Gb RAM) with a QLogic dual FC card, a IBM TS3200 tape robot with two FC LTO3 drives. And a couple of diskdrives of course
Operating system:
Centos 4.5 (with kernel 2.6.9-42.0.10.EL) - all patched up otherwise
The TS3200 does not fancy the ordinary /dev/sgXX and /dev/nstXX, so IBM has IBMtape-3.0.5-2.6.9-42.0.10.EL.i386.engr.rpm.bin that has to be installed. This must match the kernel used.
I discovered that this process upon boot tried to unload the ST module. I checked with ps aux and rmmod st did not finish. Trying to kill -9 XXXX did not help. Some digging around, and the solution was to add this line to /etc/modprobe.conf
alias st off
After a reboot, the IBMtaped process ran as it should, and dsmserv did not complain.
-= Trident =-
Hardware:
IBM x226 (3 GHz and 3 Gb RAM) with a QLogic dual FC card, a IBM TS3200 tape robot with two FC LTO3 drives. And a couple of diskdrives of course
Operating system:
Centos 4.5 (with kernel 2.6.9-42.0.10.EL) - all patched up otherwise
The TS3200 does not fancy the ordinary /dev/sgXX and /dev/nstXX, so IBM has IBMtape-3.0.5-2.6.9-42.0.10.EL.i386.engr.rpm.bin that has to be installed. This must match the kernel used.
I discovered that this process upon boot tried to unload the ST module. I checked with ps aux and rmmod st did not finish. Trying to kill -9 XXXX did not help. Some digging around, and the solution was to add this line to /etc/modprobe.conf
alias st off
After a reboot, the IBMtaped process ran as it should, and dsmserv did not complain.
-= Trident =-
