Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

tape tar error

winnietanw
Occasional Visitor

tape tar error

Hi, 

I am trying to determine if a tape is full because on 2 different tapes, im receiving 2 different kind of errors:

# uname
SunOS
# /bin/tar cvf /dev/rmt/0n /export/home
a /export/home/jerry/wlserver_10.0.tar.gz 28528 tape blocks
tar: write error: unexpected EOF

#  mt -f /dev/rmt/0n status
HP DDS-4 DAT (Sun) tape drive:
   sense key(0x13)= EOT   residual= 0   retries= 0
   file no= 8   block no= 0
#

 



provadm@01:provadm/tmp%tar cvf /dev/rmt/0n add.sh
a add.sh 1 tape blocks
tar: close error: I/O error

provadm@01:provadm/tmp%mt -f /dev/rmt/0n status
HP DAT-72 tape drive:
   sense key(0x13)= EOT   residual= 0   retries= 0
   file no= 3778   block no= 0
provadm@01:provadm/tmp%


Oct 11 13:31:19 01 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,700000/pci@0/scsi@2/st@0,0 (st0):
Oct 11 13:31:19 01        Error for Command: write file mark         Error Level: Fatal
Oct 11 13:31:19 01 scsi: [ID 107833 kern.notice]  Requested Block: 1                         Error Block: 1
Oct 11 13:31:19 01 scsi: [ID 107833 kern.notice]  Vendor: HP                                 Serial Number:    9   $DR-1
Oct 11 13:31:19 01 scsi: [ID 107833 kern.notice]  Sense Key: Volume Overflow
Oct 11 13:31:19 01 scsi: [ID 107833 kern.notice]  ASC: 0x0 (end of partition/medium detected), ASCQ: 0x2, FRU: 0x0
Oct 11 13:31:19 01 scsi: [ID 107833 kern.notice]  End-of-Media Detected

 

 


Both status shows "sense key(0x13)= EOT" unfortunately, the tar error on both append are different. any suggestion if both actually meant that the tape is full?

Many Thanks!

 

 

P.S. This thread has been moved from Data Protector Support and News Forum to Tape Libraries and Drives - HP Forums Moderator

3 REPLIES
Ralf Seefeldt
Valued Contributor

Re: tape tar error

Hi Winnietanw,

 

DAT-72 is DDS5. Are you using a DDS4 driver in you solaris server?

Are you using the same drivetype on both servers?

What is the operating system on your 2nd server?

Probably, the different OSes and different drivers result in different errormessages.

 

I agree with you, that both messages tell you the tape is full.

You could read all the data off the tape on both servers and count the blocks / bytes. Are the numbers identical?

 

What does "mt status" tell you about the tape on both servers?

 

I hope, these ideas help you a little.

Ralf

winnietanw
Occasional Visitor

Re: tape tar error

Hi Ralf,

I am not sure if DAT-72 is using a DDS4 driver. Can you advise how do i check that?

Both operating systems are SunOS.
Ralf Seefeldt
Valued Contributor

Re: tape tar error

Hi,

 

I don't know exactly how, but the devide should be in the last 3 digits of the minor devicenumber and (probably) in the devicename.

 

For HP-UX, the followin is true:

Best  maximum possible density

n         No rewinde of tape after usage --> add 4 to the last but 1 digit of minor Number of the device

b         Berkley-Style tape behaviour (instead of AT&T-Type Style) 

            --> add 80 to the last but one number of the minor number of the device

Last digit of minor number = 1 --> DDS1

If you have long devicenames like c5t3d0BEST, they should be selfdescriptive.

 

Look at all of your manpages for mt st mksf

I hope, this helps you a little.

 

bye

Ralf