05-17-2006
You could cat the file directly to tape, if you kept a record of exactly how long the file was for later.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am trying to understand the webserver log file for an error which has occured on my live web site.
The webserver access file is very big in size so it's not possible to open this file using vi editor. I know the approximate time the error occured, so i am interested in looking for the log file... (4 Replies)
Discussion started by: sehgalniraj
4 Replies
2. AIX
Hi all,
I need to write on a tape drive with AIX5.3.
How to know the name of this tape and what is the procedure to read and write on this tape?
Regards,
Tovo (2 Replies)
Discussion started by: tovohery
2 Replies
3. UNIX for Dummies Questions & Answers
How do we check 'large files' is enabled on a Unix box -- HP-UX B11.11 (2 Replies)
Discussion started by: ranj@chn
2 Replies
4. UNIX for Dummies Questions & Answers
Hi Guy`s I`m a newbie to Unix and I`m starting to love it
I got stuck donig backups of tar files to tape
I use this to find all tar files
find . -name '*.tar.*' > output
in output there would be n of file eg. 6
the size output is 156 but tar files are:
9.3M Jul 18 09:48... (1 Reply)
Discussion started by: donovan
1 Replies
5. Filesystems, Disks and Memory
I am trying to learn what command I would need to enter to tell my very old tape writer to write a large > 210 MB file from a UNIX box to 3480 tapes. I can get a single tape to write < 210 MB but if the file is large I am not aware of what command to enter to tell it to split the input file across... (0 Replies)
Discussion started by: james.hodge@eds
0 Replies
6. UNIX for Advanced & Expert Users
In a recent research experiment I was handling, I faced this task of managing huge amounts of data to the order of Terabytes and with the help of many people here, I managed to learn quite a lot of things in the whole process. I am sure that many people will keep facing these situations quite often... (2 Replies)
Discussion started by: Legend986
2 Replies
7. Shell Programming and Scripting
Hello everyone!
I have 2 types of files in the following format:
1) *.fa
>1234
...some text...
>2345
...some text...
>3456
...some text...
.
.
.
.
2) *.info
>1234 (7 Replies)
Discussion started by: ad23
7 Replies
8. Solaris
Hello everyone. Need some help copying a filesystem. The situation is this: I have an oracle DB mounted on /u01 and need to copy it to /u02. /u01 is 500 Gb and /u02 is 300 Gb. The size used on /u01 is 187 Gb. This is running on solaris 9 and both filesystems are UFS.
I have tried to do it using:... (14 Replies)
Discussion started by: dragonov7
14 Replies
9. Shell Programming and Scripting
Hello, I need to copy a 700GB tape-image file over a network. I want to start the copy process before the tape-image has finished being restored from the tape. The tape restore speed is about 78 Mbps and the file transfer speed over the network is about 45 Mbps I don't want to use a pipe, since... (7 Replies)
Discussion started by: swamik
7 Replies
10. Solaris
unix1{owadmin}% tar tvf /dev/rmt/1
-rw-rw-rw- 1021/10 0 Sep 11 17:54 2011 TinahPF_Far_32bit.segy
tar: directory checksum error
unix1{owadmin}%
i know in this tape 3 files not only one file so what can i do to view 3 files
and what is this error mean ( tar: directory checksum error... (2 Replies)
Discussion started by: ayman
2 Replies
TOPEN(3F) TOPEN(3F)
NAME
topen, tclose, tread, twrite, trewin, tskipf, tstate - f77 tape I/O
SYNOPSIS
integer function topen (tlu, devnam, label)
integer tlu
character*(*) devnam
logical label
integer function tclose (tlu)
integer tlu
integer function tread (tlu, buffer)
integer tlu
character*(*) buffer
integer function twrite (tlu, buffer)
integer tlu
character*(*) buffer
integer function trewin (tlu)
integer tlu
integer function tskipf (tlu, nfiles, nrecs)
integer tlu, nfiles, nrecs
integer function tstate (tlu, fileno, recno, errf, eoff, eotf, tcsr)
integer tlu, fileno, recno, tcsr
logical errf, eoff, eotf
DESCRIPTION
These functions provide a simple interface between f77 and magnetic tape devices. A ``tape logical unit'', tlu, is ``topen''ed in much the
same way as a normal f77 logical unit is ``open''ed. All other operations are performed via the tlu. The tlu has no relationship at all
to any normal f77 logical unit.
Topen associates a device name with a tlu. Tlu must be in the range 0 to 3. The logical argument label should indicate whether the tape
includes a tape label. This is used by trewin below. Topen does not move the tape. The normal returned value is 0. If the value of the
function is negative, an error has occured. See perror(3F) for details.
Tclose closes the tape device channel and removes its association with tlu. The normal returned value is 0. A negative value indicates an
error.
Tread reads the next physical record from tape to buffer. Buffer must be of type character. The size of buffer should be large enough to
hold the largest physical record to be read. The actual number of bytes read will be returned as the value of the function. If the value
is 0, the end-of-file has been detected. A negative value indicates an error.
Twrite writes a physical record to tape from buffer. The physical record length will be the size of buffer. Buffer must be of type char-
acter. The number of bytes written will be returned. A value of 0 or negative indicates an error.
Trewin rewinds the tape associated with tlu to the beginning of the first data file. If the tape is a labelled tape (see topen above) then
the label is skipped over after rewinding. The normal returned value is 0. A negative value indicates an error.
Tskipf allows the user to skip over files and/or records. First, nfiles end-of-file marks are skipped. If the current file is at EOF, this
counts as 1 file to skip. (Note: This is the way to reset the EOF status for a tlu.) Next, nrecs physical records are skipped over. The
normal returned value is 0. A negative value indicates an error.
Finally, tstate allows the user to determine the logical state of the tape I/O channel and to see the tape drive control status register.
The values of fileno and recno will be returned and indicate the current file and record number. The logical values errf, eoff, and eotf
indicate an error has occurred, the current file is at EOF, or the tape has reached logical end-of-tape. End-of-tape (EOT) is indicated by
an empty file, often referred to as a double EOF mark. It is not allowed to read past EOT although it is allowed to write. The value of
tcsr will reflect the tape drive control status register. See ht(4) for details.
FILES
/usr/lib/libU77.a
SEE ALSO
ht(4), perror(3F), rewind(1)
4.2 Berkeley Distribution May 15, 1985 TOPEN(3F)