Tar error...

[jbase]

Hi

While performing a simple tar extraction from DLT drive (in Sun 5.8) the following error is received....

=========

#tar xvf /dev/rmt2
tar: The block size is 16 bytes
x./dir1
x./dir1/dir2
tar: 0511-184 Cannot set the time on ./dir1: Operation not permitted
x./dir1/dir2/dir3
tar: 0511-184 Cannot set the time on ./dir1/dir2: Operation not permitted
x./dir1/dir2/dir3/PROGRAM.exe: The file access permissions do not allow the specified action
tar: 0511-193 An error occurred while reading from the media.
There is not enough memory available now.

========

- I have been assured that the tape was ok when it was written. Also there is plenty of disk space aswell as memory.

I've been trying to find out what those tar codes mean.

Regards
Raj

 

[lfoata]

Do you have all the right permissions on where you are trying to restore ? Too bad I.T. is not cash business

Luc Foata
Unix sysadmin, Oracle DBA

 

[crowe]

In responce to the "There is not enough memory available now" error, I believe the native tar command creates a file (/tmp/tar) that holds the link tables. You might try checking the /tmp FS utilization in another session while the tar archive is being "unpacked". You might be filling up /tmp.

crowe

 

[dhuuh23]

Normally, when you are creating tar archive, you cd to the directory that contains data you want to put to archive tape
and then write the command like the following:
tar cvf /dev/rmt/tape# . This means all data on the current
directory is backed to the tape; when you are extracting from the tape you write like this:
tar xvf /dev/rmt/tape1 means you are writing from tape to
the current directory. write permission is required first to
th current directory. second, you may require to know the
status of the tape or the tape may need to be rewinded before backup the data. if you think there isn't enough space in the current directory, please use du command to make sure availability of enough space in the current directory.
Jama
Jama

 

[jbase]

My collegue resolved the problem....It was the change of the Block Size that was needed. Whenever he had previously restored before via tar, the Block size was automatically detected, but for this occassion it did not and we received the messages in the output.

Cheers for the help...

Regards
Raj