A library client writing to an LTO5 drive fails with the following error :
ANR1411W Access mode for volume <volume_name> now set to "read-only" due to write error
An example of messages logged in the activity log of the library client follows.
ANR0408I Session xx started for server LIBMGR (AIX) (Tcp/Ip) for library sharing. (SESSION: xx, PROCESS: nn)
ANR8337I LTO volume TAP001L5 mounted in drive DRV01 (/dev/rmt1). (SESSION: xx, PROCESS: nn) ...
ANR1340I Scratch volume TAP001L5 is now defined in storage pool MYPOOL. (SESSION: xx, PROCESS: nn)
ANR1411W Access mode for volume TAP001L5 now set to "read-only" due to write error. (SESSION: xx, PROCESS: nn)
In this example, the library manager is running Tivoli Storage Manager V184.108.40.206 and the library client is running Tivoli Storage Manager V220.127.116.11. There are no ANR8300E, ANR8311E, ANR8302E errors logged. There is no indication of a library or drive hardware failure of any kind.
Diagnosing the problem
Verify the current configuration of the "checktapepos" server option on both the library client and the library manager. Use the following command :
q option checktapepos
In this example, the checktapepos option was set to YES on the library manager but was set to NO on the library client.
Resolving the problem
Run the following command on the library client to enable checktapepos :
setopt checktapepos yes
Make sure that all servers use the same option value. In this case, setting the checktapepos option value to YES on all library clients running V18.104.22.168 (default is NO) and setting the checktapepos option value to YES on the library manager (default is YES), solved the issue.