Direct links to fixes
APAR status
Closed as documentation error.
Error description
Messages ANR8311E, ANR8469E and ANR8996W focus on I/O errors which relate to device setting, device capability and server usage. They do not mention that an error/failure in the drive hardware itself can cause these errors as well. From an example scenario, a server trace with traceflag PVR will show : [pvr.c][14026][AgentThread]:PVR I/O agent (2275338) processing WRITE request. [pvrntp.c][3386][NtpWrite]:Writing 262144 bytes to NTP volume Volume1. [pvrntp.c][6316][NtpBuildComBlockHdr]:Building NTP Block Header - block ID = 121281 and data bytes = 262096. ][pspvr.c][4189][PvrPsDevWrite]:handle = 28 wrote = -1 requested = 262144 errno = 5 [psntpop.c][4176][DetermineResult]:Error performing WRITE operation on drive DRIVE1 (/dev/DRIVE1); errno = 5 [pspvr.c][4253][PvrPsTapeIoctl]:Tape IOCTL return code rc = -1 [psntpop.c][4333][TraceMsg]:ANR8311E An input/output (I/O) error occurred during an attempt to access drive DRIVE1 (/dev/DRIVE1) for operation WRITE. The error number (errno) is 5 and the return code (rc) is 2863.~ [pvrntp.c][9195][ErrorHandler]:tapeRc = 2863 rc = 2813 [pvr.c][14462][AgentThread]:PVR I/O agent (2275338) finished WRITE request; rc=2813. [pvr.c][14026][AgentThread]:PVR I/O agent (2275338) processing DISMOUNT request. [pvrntp.c][4273][NtpDismount]:Dismounting NTP volume Volume1. [mms.c][1679][MmsDismountVolume]:Dismounting volume Volume1 from drive DRIVE1 (/dev/DRIVE1) in library LIBRARY1. [mmsscsi.c][2764][ScsiDismountVolume]:Dismounting volume Volume1 from drive DRIVE1 (/dev/DRIVE1) in library LIBRARY1. [mmsscsi.c][14085][BeginActivity]:Beginning DISMOUNT activity for SCSI library LIBRARY1. [mmsscsi.c][12600][MoveVolume]:Moving volume in library LIBRARY1 from 274 to 1379 emptyVolFlag = 0. [pvrntp.c][5600][NtpEjectVolume]:Ejecting volume from drive DRIVE1 (/dev/DRIVE1). [pspvr.c][4253][PvrPsTapeIoctl]:Tape IOCTL return code rc = -1 [psntpop.c][4176][DetermineResult]:Error performing OFFL operation on drive DRIVE1 (/dev/DRIVE1); errno = 16 [pspvr.c][4253][PvrPsTapeIoctl]:Tape IOCTL return code rc = -1 [psntpop.c][4333][TraceMsg]:ANR8311E An input/output (I/O) error occurred during an attempt to access drive DRIVE1 (/dev/DRIVE1) for operation OFFL. The error number and the return code (rc) is 2863.~ [psntpop.c][1897][NtpOpGetLogPage]:Getting log page 31 for drive DRIVE1 (/dev/DRIVE1). [pspvr.c][4253][PvrPsTapeIoctl]:Tape IOCTL return code rc = -1 [psntpop.c][4176][DetermineResult]:Error performing GETLOGSENSE operation on drive DRIVE1 (/dev/DRIVE1); errno = 16 [pspvr.c][4253][PvrPsTapeIoctl]:Tape IOCTL return code rc = -1 [psntpop.c][4333][TraceMsg]:ANR8311E An input/output (I/O) error occurred during an attempt to access drive DRIVE1 (/dev/DRIVE1) for operation GETLOGSENSE. The error number (errno) is 16 and the return code (rc) is 2863.~ [pvrntp.c][10970][DisableAppendOnly]:optionsP->checkTapePos = 3 driveP appendOnly = 1 [pspvr.c][4253][PvrPsTapeIoctl]:Tape IOCTL return code rc = -1 [psntpop.c][4176][DetermineResult]:Error performing QUERYAPPENDONLY operation on drive DRIVE1 (/dev/DRIVE1); errno = 16 [pspvr.c][4253][PvrPsTapeIoctl]:Tape IOCTL return code rc = -1 [psntpop.c][4333][TraceMsg]:ANR8311E An input/output (I/O) error occurred during an attempt to access drive DRIVE1 (/dev/DRIVE1) for operation QUERYAPPENDONLY. The error number (errno) is 16 and the return code (rc) is 2863.~ [psntpop.c][3331][NtpOpQueryAppendOnly]:NptOpQueryAppendOnly returned rc = 2863. [pvrntp.c][11044][TraceMsg]:ANR8996W The server is unable to query or enable append-only mode on tape drive DRIVE1. ~ [pvrntp.c][11070][DisableAppendOnly]:rc = 2863 supported = 0 appendOnly = 0 driveP appendOnly 1 [mmsscsi.c][12723][MoveVolume]:ejectRc = 2813 [mmsscsi.c][12741][MoveVolume]:abnormal exit rc = 0 openRc = 0 ejectRc = 2813 [mmsscsi.c][2803][ScsiDismountVolume]:Could not move volume Volume1 from drive DRIVE1 (/dev/DRIVE1) in library LIBRARY1; rc = 2813. [mmsscsi.c][2808][TraceMsg]:ANR8469E Dismount of 3592 volume Volume1 from drive DRIVE1 (/dev/DRIVE1) in library LIBRARY1 failed.~ [mmsscsi.c][2816][ScsiDismountVolume]:Move failed with compCode = 317. [pspvr.c][4036][PvrPsCloseDevice]:Device with handle 28 is closed. [mmsscsi.c][14268][EndActivity]:Ending DISMOUNT activity for SCSI library LIBRARY1. [pvr.c][14462][AgentThread]:PVR I/O agent (2275338) finished DISMOUNT request; rc=2813. From the trace it can be seen that the initial error happened on the write operation. In this case, the failure is related to a hardware error (tape). After this failure has occurred, the server failed with DISMOUNT and QUERY operations. The server displayed ANR8311E, ANR8996W and ANR8469E messages - however, these messages do not mention that a possible hardware failure can be the reason for the I/O error. IBM Spectrum Protect Versions Affected: IBM Spectrum Protect Server 8.1.x versions on AIX, Linux, and Windows. Additional Keywords: TSM, "Storage Protect".
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Storage Protect server users. * * * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * * * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. * * This problem is currently projected to be fixed in level * * 8.1.20.000. * * Note that this is subject to change at the discretion of * * IBM. * ****************************************************************
Problem conclusion
This problem was fixed. Affected platforms for reported release: AIX, Linux, and Windows. ANR8311E An input/output (I/O) error occurred during an attempt to access drive ABCDEF for operation XYZ. The error number (errno) is 123 and the return code (rc) is 456. Explanation This error can occur if the DEVICE parameter is incorrectly specified, if the drive is powered off, if the Windows Group Policy blocks access to removable devices or if the drive has hardware errors. SystemAction System operation continues, but the specified operation fails. UserResponse To resolve the issue, take the following steps: 1. Ensure that the drive is powered on and ready and then retry the operation. 2. If the operation continues to fail, verify whether the DEVICE parameter that is associated with the drive was specified correctly on the DEFINE PATH command. To verify the value of the DEVICE parameter, issue the QUERY PATH command. For example, if the source is BOSTON1, issue the following command: query path boston1 format=detailed 3. If the DEVICE parameter was incorrectly specified, use the UPDATE PATH command to update the parameter value. 4. If you are using a Microsoft Windows operating system, review the information in this step and take any appropriate action. If the errno value is 3, the Windows Group Policy is running on the host system and the Audit object access policy setting is defined. The Windows Group Policy, especially the Audit object access policy setting, can block access to I/O from the host system. If this issue occurs, running tape devices can no longer be detected by tape device drivers. To use tape devices on a Windows operating system with Windows Group Policy enabled, take one of the following actions: - Ensure that no value is defined for the Audit object access policy setting. Tip: To change the setting, complete the following steps: a. Open the Group Policy Management Console and click the Settings section for the target group policy object to access the Local Group Policy Editor. b. In the navigation pane, click Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Audit Policy. - Ensure that the Windows command gpupdate /force is not issued while I/O is running with the tape devices and that the Audit object access policy setting is not defined. - Ensure that the <keyword keyref="longprod"/> server is not in the Active Directory group policy. - Disable the Windows Group Policy. For more information about diagnosing and resolving the error, see technote 298703 (https://www.ibm.com/support/pages/node/298703). Or go to the Microsoft documentation website and search for "Monitor the use of removable storage devices" (https://docs.microsoft.com/en-us/windows/security/threat-protec tion/auditing/monitor-the-use-of-removable-storage-devices). 5. Retry the operation that failed. ANR8996W The server is unable to query or enable append-only mode on tape drive ABCDEF Explanation The server was unable to query or enable append-only mode because the tape drive does not support append-only mode or there is a hardware error in the drive. SystemAction System operation continues, but the server does not query or enable append-only mode for the tape drive during this mount operation. UserResponse If the tape drive is in a virtual library, see the documentation from the virtual library vendor to determine whether the drive supports append-only mode. If the tape drive does not support append-only mode, contact the tape drive vendor for assistance. If you want to use append-only mode and the tape drive supports append-only mode, complete the following steps: 1. Specify the CHECKTAPEPOS server option and select either the YES or DRIVEONLY parameter values. 2. Retry the mount operation. The server will attempt to enable append-only mode the next time a volume is mounted. 3. If the issue persists, contact the tape drive vendor for assistance. If this is tape drive in a physical library, see any error messages related to the hardware in the server activity log file.
Temporary fix
Comments
APAR Information
APAR number
IT44227
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
81L
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-07-25
Closed date
2023-08-03
Last modified date
2023-08-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"81L"}]
Document Information
Modified date:
06 March 2024