Wednesday, July 16, 2008
We recently experienced an issue with a drive that we could not remove or force delete. What was happening is that TSM continually tried to dismount a volume from this drive but failed. The tape it was trying to dismount was in its home slot and not in the drive and the drive showed idle in ACSLS. TSM would not let us remove the path for it so we could not eliminate the problem. We tried a reboot and the dismount retries came up with the TSM server and NOTHING could get rid of the issue. Even turning the drive off in the library did not eliminate the "phantom" dismount attempt by TSM (We even removed the device from AIX to no avail). So did my manager finally find to be the issue? It turned out to be an incorrect WWN for the drive. How it got changed we have no idea...but it did and it caused days worth of headaches and flooded the activity log with errors. So it you ever come across a "phantom" drive check the WWN and make sure you don't suffer as we did.
Posted by Chad Small at 7/16/2008
Subscribe to: Post Comments (Atom)
changing WWNs - what type of library do you have? I have found recently that in SL8500 the WWN dependent on the drive position. When we swapped driveA and driveB, then driveA had WWNB and driveB had WWNA.
Could that be the cause?