Anr8779e Unable To Open Drive Error Number=16
Contents |
ANR8779E TSM SYMBOLIC LINK RESETDRIVE DPF DISMOUNT LAN FREE Technote (troubleshooting) Problem(Abstract) The Server activity log reports the following message after a LAN Free client fails: ANR8779E Unable anr8779e error number=5 to open drive
Anr8779e Error Number 46
Operating System error that means the device is busy and could not be opened by the TSM Server. Cause Symbolic links anr8779e error number=110 are used for the DEVICE parameter in the DEFINE PATH command. Normally setting RESETDRIVE=YES in the library definition will have the effect of issuing a LUN reset by the Server to the drives
Unable To Open Drive Error Number 46
held by a failed LAN Free client. The LUN reset command fails when the drive path parameter is a symbolic link to the actual drive path. The Tivoli Storage Manager server will report the error for each drive allocated to the LAN Free client, and will repeat the error once every minute when the Server attempts to reclaim the drive. This error will be reported in the activity anr8779e error number=6 log indefinitely until actions are taken to free the drive. Resolving the problem Redefine the drive paths on the Tivoli Storage Manager server to use the correct drive path file names. Symbolic links for drive paths are not a supported configuration for device definitions. Make sure the library definition has the RESETDRIVE parameter set to YES when using LAN Free clients; this will allow the server to reclaim the drives from Storage Agent clients that have failed. When RESETDRIVE is working the following line will appear in a TSM Server PVR trace: PvrResetDev called for /dev/rmtX. Note: If the Storage Agent IBM device driver has DPF (Dynamic Path Failover) feature enabled, the library manager will not be able to use LUN RESET to clear the drive reservation. The reason is LUN RESET can not clear the reservation made by Persistent Reserve used in DPF. Document information More support for: Tivoli Storage Manager Server Software version: All Supported Versions Operating system(s): AIX, IRIX, Linux, Solaris, TRU64 UNIX Software edition: All Editions Reference #: 1249613 Modified date: 2010-01-04 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
on drive OPEN rggenis rggenis12 TSM SAN DISCOVERY ERRNO 16 CONFLICT EBUSY ANR8311E ANR8779E reservation conflicts reservations reserve reserved conflict
Anr8779e Error Number=13
Technote (troubleshooting) Problem(Abstract) Diagnosing and resolving ANR8779E with error number 16 /
Tsm Anr8779e
170 (EBUSY) reported by the IBM Spectrum Protect server during drive OPEN operations. Symptom ANR8779E Unable to open anr8779e error number=2 drive /dev/rmtX, error number = 16 ANR8779E Unable to open drive mtx.y.z.n error number=170 Cause What does message ANR8779E with error number 16/170 (EBUSY) on OPEN mean? This is a http://www-01.ibm.com/support/docview.wss?uid=swg21249613 return code returned to IBM Spectrum Protect (formerly Tivoli Storage Manager) by the operating system via the device driver (IBMtape or TSMtape) when attempting to open a device special file. On Unix operating systems, errno 16 means that the file was busy, or EBUSY. On Windows operating systems, the errno is 170, but the meaning is the same. This http://www-01.ibm.com/support/docview.wss?uid=swg21579521 error indicates that the operating system could not satisfy IBM Spectrum Protect's request to open the device, because it was in use somewhere else. When dealing with special device files, this means that the device has an open reservation on it through a different HBA, which typically means on a separate host (but could be the same host if multiple HBA's are in use). What sequence of events occur during a library sharing tape volume mount? The Library Manager is responsible for drive allocation and assignments. Once a drive is as allocated, the owning host (Library Client/STA) ensures exclusive ownership by "reserving" the drive and the Library Manager maintains the drive inventory and owners. The following is an example of the sequence of events that tape place for a single drive assignment in a library sharing environment: 1. A library client (LC) or storage agent (STA) requires a tape mount resource. 2. The LC/STA requests a drive from the library manager (LM). 3. The LM locates an available drive, reserves the drive, mounts a tape, and verif
OR IS DISABLED. AIX A fix is available IBM Tivoli Storage Manager V5.5 Fix Pack 2 (5.5.2) Server Downloads Subscribe You can track all active APARs for this component. http://www-01.ibm.com/support/docview.wss?uid=swg1IC57753 APAR status Closed as program error. Error description Customers' may run into an https://adsm.org/forum/index.php?threads/anr8779e-unable-to-open-drive-dev-rmt1-error-number-11.15520/ issue when TSM discovers a serial number mismatch on a drive it attempts to open. This will happen when the drive we successfully opened reports a different serial number than what is stored in the TSM database, indicating that the wrong drive was opened. When the serial mismatch occurs, TSM attempts to resolve the mismatch error number with SAN discovery. However, if SAN Discovery fails or is disabled, then not only will TSM fail to open the intended drive, it will additionally neglect to close the wrong drive it had just opened while handling the SAN discovery failure or its disablement. Thus, there will be a SCSI reservation left on a drive that will not be released unless TSM or that drive is recycled. . anr8779e error number If the above situation occurs, then the error number=16 will be seen on subsequent attempts to open the drive with a stale reservation leftover from this described behavior. Thus, the server reporting the error number=16 generally did not cause the problem, but was only affected by the aftermath of this situation. In many cases the TSM server or storage agent that left the stale reservation will throw an ANR8963E error message. . Customer/L2 Diagnostics (if applicable) Messages seen: ANR8779E Unable to open drive drive_name, error number=16 ANR8963E Unable to find path to match the serial number defined for drive drive name in library library nam . Tracing MMS NA PVRVOL PVRMP may show trace points similar to the following: . 11:08:10.377 [16][pvr.c][5399]: (PvrOpenTapeDrive) Drive OXMF08R04 devtype 25 open rc 94 with handle 46 nonDelayFlag 0 will call PvrOpenDevice again with nodelay 11:08:10.394 [16][pspvr.c][2775]: device /dev/rmt12 is opened with handle 10 pass handel 10 back 11:08:10.394 [16][pvr.c][5406]: (PvrOpenTapeDrive) Drive OXMF08R04 devtype 25 open rc 0 with handle 10 and nonDelayFlag is TRUE. 11:08:10.394 [16][mmsdrive.c][7922]: MmsCheckTapeId: Checking drive OXMF08R04 information with openRc 0 ... 11:13:26.127 [16][pspvr.c][2678]: PvrDiscoverPath: rc = 34 result = 268 11:13:26.128 [16][mmsdrive.c][8478]: (MmsCheckTapeId) PvrDiscoverPath did not find a path to
answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts. Please Give Thanks to Those Sharing Their Knowledge Forum Rules (PLEASE READ BEFORE POSTING) ANR8779E Unable to open drive /dev/rmt1, error number=11. Discussion in 'Tape / Media Library' started by Jacob_6, Oct 13, 2008. Jacob_6 ADSM.ORG Senior Member Joined: Jul 22, 2008 Messages: 207 Likes Received: 5 Occupation: TSM Admin, Netbackup Admin Location: Dallas, Texas I am getting these errors on my system, searched the IBM website to no avail. Drives are LTO1 Drives in a 3584 library. Any assistance would be appreciated. ANR8779E Unable to open drive /dev/rmt1, error number=11. Thanks much. Jacob_6, Oct 13, 2008 #1 ADSM.ORG Sponsor heada ADSM.ORG Moderator Joined: Sep 23, 2002 Messages: 2,560 Likes Received: 168 Occupation: Storage Administrator Location: Indiana Since you are trying to access /dev/rmt1 I am assuming you are on AIX. Have you verified that /dev/rmt1 exists and is available (lsdev -Cc tape) If it is available, is it the drive you think it is? Compare serial number with lscfg -vl rmt1 to what TSM thinks it is, q drive {libr} {drive} f=d -Aaron heada, Oct 13, 2008 #2 Jacob_6 ADSM.ORG Senior Member Joined: Jul 22, 2008 Messages: 207 Likes Received: 5 Occupation: TSM Admin, Netbackup Admin Location: Dallas, Texas anr8779e Sorry should have mentioned that I am on AIX 5.2 running TSM 5.2.3, I don't have the option to do an upgrade. I checked the lsdev output and the drive is available. I checked the lscfg and the serial matches the TSM serial number wh