Quantcast
Channel: Symantec Connect
Viewing all articles
Browse latest Browse all 22530

io_ioctl_ndmp (MTBSF) failed: (NDMP_DEV_NOT_OPEN_ERR) (bptm.c.8757)....Could this be the possible drive failure issue coming in sight???

$
0
0
I need a solution

Hello Experts,

Today I found  one of our NDMP backup failed with the error code 84 media write error.

I check the bptm logs at the time of the failure which are below :

10:20:03.731 [22081] <2> log_media_error: successfully wrote to error file - 01/28/14 10:20:03 270934 0 WRITE_ERROR IBM.ULTRIUM-TD5.000
10:20:03.731 [22081] <2> write_backup: write_data() returned, exit_status = 84, CINDEX = 0, TWIN_INDEX = 0, backup_status = -8
10:20:03.731 [22081] <2> io_terminate_tape: writing empty backup header, drive index 0, copy 1
10:20:03.731 [22081] <2> io_terminate_tape: reposition to previous tapemark and rewrite header
10:20:03.731 [22081] <2> io_ioctl: command (2)MTBSF 1 0x0 from (bptm.c.8757) on drive index 0
10:20:03.733 [22081] <16> io_ioctl: io_ioctl_ndmp (MTBSF) failed on media id 270934, drive index 0, return code 6 (NDMP_DEV_NOT_OPEN_ERR) (bptm.c.8757)
10:20:03.733 [22081] <2> send_MDS_msg: DEVICE_STATUS 1 12300 amerusahdcnbk01 270934 4001116 IBM.ULTRIUM-TD5.000 2000041 POSITION_ERROR 0 0
10:20:03.733 [22081] <2> TAO: TAO (22081|1) RT Timeout is <1800000>
10:20:03.733 [22081] <2> TAO: TAO (22081|1) Connection Timeout is <0>
10:20:03.734 [22081] <2> TAO: TAO (22081|1) - Transport_Cache_Manager::is_entry_idle_i, state is [0]
10:20:03.734 [22081] <2> TAO: TAO (22081|1) - Synch_Invocation::invoke_i, timeout on recv is <1799999>
10:20:03.741 [22081] <2> TAO: TAO (22081|1) Synch_Invocation::invoke_i, timeout after recv is <1799985> status <1>
10:20:03.741 [22081] <2> log_media_error: successfully wrote to error file - 01/28/14 10:20:03 270934 0 POSITION_ERROR IBM.ULTRIUM-TD5.000
10:20:03.741 [22081] <2> io_close: closing /usr/openv/netbackup/db/media/tpreq/drive_IBM.ULTRIUM-TD5.000, from bptm.c.16433
10:20:03.743 [22081] <2> NdmpMediaSession_close_public_and_ndmpagent[0]: closing public session, force = 0, agent_session_index = 0
10:20:08.744 [22081] <2> NdmpMediaSession: NDMP SDK: stub called for missing shared library entry "ndmp_get_error_name"
10:20:08.744 [22081] <2> NdmpMediaSession: NDMP SDK: continuing without looking up error name; returning "?"
10:20:08.744 [22081] <2> io_close: ignore ndmp close error, ?
10:20:08.744 [22081] <2> drivename_write: Called with mode 1
10:20:08.744 [22081] <2> drivename_unlock: unlocked
10:20:08.744 [22081] <2> drivename_close: Called for file IBM.ULTRIUM-TD5.000
10:20:08.744 [22081] <2> tpunmount: NOP: MEDIA_DONE 0 26654 0 270934 4001116 0 {BC336170-87E5-11E3-B280-A88242227807}
10:20:08.744 [22081] <2> send_brm_msg: EXIT
10:20:08.744 [22081] <2> bptm: EXITING with status 84 <----------
 

 

However,

The backups are running fine on this drive after this failure. No error reported again.

I searched  and found the best matching  tech Note TECH59178

It states that it Requires tape drive hardware problem to be resolved.

Could this be the possible hardware prolem coming in sight?? please advise

 

Env. Detials:

Master/ Media : 7505/Linux 2.6.32-358.6.1.el6.x86_64

Local NDMP ( Netapp FAS 3250)

Drives : IBM.ULTRIUM-TD5


Viewing all articles
Browse latest Browse all 22530

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>