cancel
Showing results for 
Search instead for 
Did you mean: 

Tapes at an interval are getting freezed

abhas_mangal
Level 3

I have noticed two tapes one on 23rd Oct and other on 25th Oct,09 getting freezed due to the same reason in bptm log file:

grep -i 539L3 /usr/openv/netbackup/logs/bptm/log.102309 | tail -15
08:28:38.357 [25148] <2> io_position_for_write: position media id 0539L3, copy 2, current number images = 19
08:33:15.258 [25838] <2> report_drives: MEDIA = 0539L3
08:38:25.710 [25148] <16> io_ioctl: ioctl (MTFSF) failed on media id 0539L3, drive index 1, I/O error (bptm.c.6869)
08:38:25.710 [25148] <2> send_MDS_msg: DEVICE_STATUS 1 128851 backup-1 0539L3 4000092 HP.ULTRIUM3-SCSI.001 2000010POSITION_ERROR 0 0
08:38:25.769 [25148] <2> log_media_error: successfully wrote to error file - 10/23/09 08:38:25 0539L3 1 POSITION_ERRORHP.ULTRIUM3-SCSI.001
08:38:25.788 [25148] <2> tpunmount: NOP: MEDIA_DONE 0 192450 0 0539L3 4000092 180
08:38:25.796 [25148] <2> bptm: Calling tpunmount for media 0539L3
08:38:25.796 [25148] <2> send_MDS_msg: MEDIA_DONE 0 192450 0 0539L3 4000092 180
08:38:27.528 [26209] <2> bptm: INITIATING (VERBOSE = 2): -unload -dn HP.ULTRIUM3-SCSI.001 -dp /dev/rmt/1cbn -dk 2000010 -m0539L3 -mk 4000092 -mds 8 -alocid 128851 -jobid -1255869866 -jm
08:38:27.838 [26209] <2> parse_resource_strings: MEDIADB 1 128851 0539L3 4000092 ------ 20 1255425867 1255735778 1258037715 0455082848 19 17 3 2 0 0 1024 0 1777722 0
08:38:27.839 [26209] <2> parse_resource_strings: VOLUME 1 0539L3 4000092 000539L3 DataStore *NULL* *NULL* 24 8 0 11 0{00000000-0000-0000-0000-000000000000} 0

The tape details are:
/usr/openv/volmgr/bin/vmquery -m 0539L3
================================================================================
media ID:              0539L3
media type:            1/2" cartridge tape 3 (24)
barcode:               000539L3
media description:     Added by Media Manager
volume pool:           DataStore (2)
robot type:            TLD - Tape Library DLT (8)
robot number:          0
robot slot:            11
robot control host:    backup-1
volume group:          000_00000_TLD
vault name:            ---
vault sent date:       ---
vault return date:     ---
vault slot:            ---
vault session id:      ---
vault container id:    -
created:               Sat Jun 27 00:32:14 2009
assigned:              Tue Oct 13 11:24:27 2009
last mounted:          Fri Oct 23 08:28:38 2009
first mount:           Sat Jun 27 00:37:18 2009
expiration date:       ---
number of mounts:      21
max mounts allowed:    ---
status:                0x0

The tape was also mounted successfully before and used, but this time it got freezed automatically by Netbackup.
Please guide me on what is causing the two tapes to get freezed.
The Netbackup version is 6.0MP5. Tape Library is C4StorageTek.
Please let me know if you have any queries in understanding the problem. Also convey me if you need any more information.
 

5 REPLIES 5

abhas_mangal
Level 3
I also refered http://www.symantec.com/connect/forums/frozen-tapes-what-do and came to know that my Staging jobs are getting failed with error code 96.
Meanwhile I will keep a check on the tapes and post if others are also getting freezed.

Stumpr2
Level 6
Have you determined yet if it is the tape drives or the tapes that is causing the errors?
Have you tried doing a verify on the tape?

stu52
Level 5
Please check your tapes to ensure that they are not write-protected.  If they are and you attempt to write to them, they will get frozen.  I have seen people write-protect their tapes when they send them off-site and then forget to move the tab to un-write-protect them when they put them back into the library.

Mike_Gavrilov
Moderator
Moderator
Partner    VIP    Accredited Certified
  1. Try to get media content from this tape (unfreeze it, run bpmedialist -mcontents -ev 0539L3, will this tape be frozen again?)
  2. If it's not possible to get mcontent from this tape try to read/write this media in another drive to understand what is the root cause - tape or drive.
  3. Check drive clean state (run tpclean)
  4. Check Tape Alerts on media.
  5. Check media errors
  6. Check Library's logs.
Generally POSITION_ERROR mean that drive can't find end of file. (MTFSF command will leave the tape positioned just after that same EOF).
After some test you'll be able to make any suggestions about cause if this behavior.

stu52
Level 5
abhas,

where is the message from the bptm log that has the "FREEZING MEDIA" message?

Also, you mention that there were other jobs that got error 96 which is "unable to allocate new media".  What error did you get for the job that mounted this tape?