Reading tape and redirecting output to a file. In this case, the operating system showed that the tape itself is damaged.
This doesn't need to be the case. If the tape was written with another blocksize (default blocksize depend on hardware, so we do not know what yours is) then trying to read will result in a "tape damaged" - in fact it is, in a way, because it was formatted differently.
Hi,
I' using a sun solaris server, I would like to known if there is the possibility to control how many space is free on a tape and how I can delete a single file on a tape.
Thanks
DOMENICO (3 Replies)
Hi there: I'm new here
Can anyone help me:
I have DS15 Alpha server : Unix 5.1B
Now i need to connect a DLVT VS80 1U Rackmount Tape Drive unit.
What is the exact comman to mount the DLTape IV??
How do i make backuo @ copy file to the tape?
Thanx to all (0 Replies)
I am having my 14 Aix 5.3 servers on bladecenters connected with my Tape Library.
I had a backup scheduled on tape library but after taking backup successfully,
Now,
Question 1:-
I wanted to restore backup but tape library could not recognize the tape and I get I/O error in TSM. I think it... (0 Replies)
when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several:
Status : ready beginning-of-tape
soft errors : 0
hard errors: 2
underruns: 5
My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Hi all,
I would like to know what would happen if the tape (media) is not placed on the drive and a tar command is executed to backup on the tape.
My problem is that tar command hanged for multiple days instead of throwing the error,
Is it valid behaviour?
I was unable to test the... (4 Replies)
hello,
I am facing this problem when trying to prepare AIX 5.3 for Veritas Backup:
Veritas Software is not able to communicate properly with our tape library
When we tried to run these commands here's the output
# cfgmgr -l fscsi0
# cfgmgr -l fscsi2
# cfgmgr -l fscsi1
cfgmgr:... (3 Replies)
I could not delete the tape in AIX
This is the steps which i used .. but still it did not deleted .. !
server/root>lscfg -l rmt0
rmt0 U789D.001.DQD298Y-P1-C5-T2-L6-L0 Other SCSI Tape Drive
server/root>
server/root>
server/root>lsdev -l rmt0 -F parent
scsi3... (3 Replies)
Hello,
We need to make a copy of a backup tape, using the 2 tape recorders in IBM 3582 Tape Library
We tried tu use "tcopy", it seems to work fine (no error messages) but we aren't sure if we can rely on it.
my question is how to check if the copy succeded or not, but i also want to know... (3 Replies)
I am using a 4mm tape to backup my Unix system. However, I wanted to make a copy all of the files and archive headers (or just the archive headers if that's possible) created on one of my tapes to another 4mm tape. I only have one tape drive. Is there a command that will complete such task? ... (1 Reply)
Discussion started by: acoco
1 Replies
LEARN ABOUT V7
tm
TM(4) Kernel Interfaces Manual TM(4)NAME
tm - TM-11/TU-10 magtape interface
DESCRIPTION
The files mt0, ..., mt7 refer to the DEC TU10/TM11 magtape. When closed it can be rewound or not, see below. If it was open for writing,
two end-of-files are written. If the tape is not to be rewound it is positioned with the head between the two tapemarks.
If the 0200 bit is on in the minor device number the tape is not rewound when closed.
A standard tape consists of a series of 512 byte records terminated by an end-of-file. To the extent possible, the system makes it possi-
ble, if inefficient, to treat the tape like any other file. Seeks have their usual meaning and it is possible to read or write a byte at a
time. Writing in very small units is inadvisable, however, because it tends to create monstrous record gaps.
The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files. When foreign tapes
are to be dealt with, and especially when long records are to be read or written, the `raw' interface is appropriate. The associated files
are named rmt0, ..., rmt7. Each read or write call reads or writes the next record on the tape. In the write case the record has the same
length as the buffer given. During a read, the record size is passed back as the number of bytes read, provided it is no greater than the
buffer size; if the record is long, an error is indicated. In raw tape I/O, the buffer must begin on a word boundary and the count must be
even. Seeks are ignored. A zero byte count is returned when a tape mark is read, but another read will fetch the first record of the new
tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO tp(1)BUGS
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward
and backward record and file spacing and to write an EOF mark.
TM(4)