1835456 Members
2922 Online
110078 Solutions
New Discussion

tar error

 
SSP_1
Regular Advisor

tar error

Hi,

Does anyone come across the following error :-
Tar: tape error (5)

I am getting this error almost for 7 medias when I am trying "tar -tvf /dev/rmt/1mn" for reading the tar archives.

Regards
Obstacles exist to challenge you to keep going. Not to quit.
4 REPLIES 4
Alex Glennie
Honored Contributor

Re: tar error

It's most likely due to tape head problem or the tape media. Try the same tape in a different drive ? If it works OK in the different drive clean the head ?
Paula J Frazer-Campbell
Honored Contributor

Re: tar error

Hi
Tar error codes:-
exit(0)
no error & no warning.

exit(1)
Tar: cannot create temporary file (%s)
Invalid blocksize. (Max %d)
tar: blocksize %d too big, can't get memory
tar:Invalid or non-existent device file %s
Can only create standard output archives
tar: cannot open %s
tar: option not supported for this device %s
tar: cannot write to %s: write protected
tar: usage tar [-]{txruc}[eONvVwAfblhm{op}][0-7[lmh]] ......
Attempt to create archive of no files. Nothing dumped.
tar: cannot preserve extent attributes for %s. aborting...
Tar: cannot create temporary file (%s)
Invalid blocksize. (Max %d)
tar: blocksize %d too big, can't get memory
tar:Invalid or non-existent device file %s
Can only create standard output archives

exit(2)
directory checksum error
tar: %s: HELP - extract write error
tar: Cannot close %s
Tar: tape write error

exit(3)
Tar: tape read error
Tar: tape blocksize error
Tar: blocksize = 0; broken pipe?
Tar: error! blocksize changed

exit(4)
Tar: tape backspace error
Tar: ioctl to write filemarks failed (%d). aborting...
Tar: ioctl to determine device online failed. aborting...

exit(5)
tar: Cannot change directory to '%s'
tar: Path '%s' skipped
tar: cannot open %s
Missing links to %s
tar: %s: cannot access file
tar: Out of memory. Cannot detect symbolic link loops
tar: Loop of symbolic links detected, tar terminated
tar: cannot stat %s. Not dumped.
tar: Size of %s > %s. Not dumped.
tar: %s: directory read error
tar: %s: directory read error
tar: %s: symbolic link too long
tar: can't read symbolic link
tar: %s: cannot open file
tar: %s: link to name too long
Out of memory. Link information lost
%s: file changed size
tar: %s is not a file. Not dumped
tar: %s: symbolic link failed
%s: cannot link
tar: %s couldn't create character device
tar: %s couldn't create block device
tar: %s couldn't create fifo
tar: %s couldn't create directory
tar: %s couldn't create directory
tar: %s - cannot create
tar: chmod failed
tar: chown failed
tar: couldn't get uname for uid %d
tar: couldn't get gname for gid %d
tar: pwd failed
tar: %s: pathname too long
tar: %s: prefix too long
tar: %s: file name too long
%s: file name too long

NOTE: exit code is condsidered as 'NONFATAL_ERRCODE'



HTH

Paula
If you can spell SysAdmin then you is one - anon
Francois Bariselle_3
Regular Advisor

Re: tar error

It's really due to tape head problem. Call your support.

good luck.
Fais la ...
Helen French
Honored Contributor

Re: tar error

hey,

1)try reading this media in any other drive/server.

2) Test read and write on the same drive with any other command. eg: cpio, fbackup etc.

3) If it's a drive problem, try cleaning it and see or replace it.

HTH,
Shiju
Life is a promise, fulfill it!