Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

backup problem

Status
Not open for further replies.

230173

MIS
Jun 22, 2001
208
SG
Does anybody know what this problem is?
Where can i find these errornumbers?

a /oradata4/prodenv/xxxxxx
tar: 0511-193 An error occurred while reading from the media.
There is an input or output error.
tar: /dev/rmt1: The requested resource is busy.
tar: /dev/rmt1: The device is not ready for operation.
tar: /dev/rmt1: There is an input or output error.
tar: /dev/rmt1: The device is not ready for operation.
/dev/rmt1: The device is not ready for operation.
Job number is: 317
Job number is: 318
$
 
i'll give a little more info.
I tried to backup on a DLT tapedrive.
After a fiew .dbf files are backuped i get this error message.
 
Check the error report (errpt -a | pg) for any HW related errors.
The error you have listed is stnd out from tar. Tape drives are fun to troubleshoot, because there can be so many different items that "make them complain". But I would start by cleaning the drive 3 times, and getting a new tape.
One thought in the back of my mind is that I do not believe tar will keep a DLT in streaming mode, which means your performance (through-put) is probably not as good as it could be. If the drive is doing a lot of re-tensioning, an error might have occured there as well.
You might try a different utility, like cpio an see if you get the same I/O error on that tape drive.

crowe
 
Just as Crowe said...........however it looks like two jobs are piggybacked on each
other...Job 317 and 318........(was it in a script?) If the one was not finished and the other started...you would get the busy stuff..............

0511-193
An error occurred while reading from the media
Possible Causes
You issued the tar command to read an archive from a tape device that has a
different block size than when the archive was created.
or
The tape is damaged.

Procedures for Recovery
From the command line, run the tctl command to check the tape
block size.

tctl -f /dev/rmt# status

Use the chdev command to change the block size, for example:
chdev -1 rmt0 -a block size=0

Check the error log for tape errors:
errpt -a
-=--------------------------------

AIX Command Default Block Size RECOMMENDATIOIN

backup 32768 or 51200 Will use either 32768 or 51200
depending on if 'backup' is
by name ( -i ) or not. No
user change is required

tar 10240 There is an error in the manual
that states a 512KB block size.
The user needs to set the
Blocking Parameter to -N64

cpio n/a The user needs to set the
Blocking Parameters to -C64

dd n/a The user needs to set the
Blocking Parameter to bs=32K
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top