Sponsored Content
Full Discussion: Writing large files to tape
Top Forums UNIX for Dummies Questions & Answers Writing large files to tape Post 302073779 by Corona688 on Wednesday 17th of May 2006 01:28:02 PM
Old 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

Large files

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

Writing in a tape drive

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

large files?

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

Writing tar file to tape

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

Writing files from Unix to 3480 Tape

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

Planning on writing a Guide to Working with Large Datasets

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

Divide large data files into smaller files

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

How to safely copy full filesystems with large files (10Gb files)

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

Start copying large file while its still being restored from tape

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

files in tape

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
TP(1)							      General Commands Manual							     TP(1)

NAME
tp - manipulate tape archive SYNOPSIS
tp [ key ] [ name ... ] DESCRIPTION
Tp saves and restores files on DECtape or magtape. Its actions are controlled by the key argument. The key is a string of characters con- taining at most one function letter and possibly one or more function modifiers. Other arguments to the command are file or directory names specifying which files are to be dumped, restored, or listed. In all cases, appearance of a directory name refers to the files and (recursively) subdirectories of that directory. The function portion of the key is specified by one of the following letters: r The named files are written on the tape. If files with the same names already exist, they are replaced. `Same' is determined by string comparison, so `./abc' can never be the same as `/usr/dmr/abc' even if `/usr/dmr' is the current directory. If no file argument is given, `.' is the default. u updates the tape. u is like r, but a file is replaced only if its modification date is later than the date stored on the tape; that is to say, if it has changed since it was dumped. u is the default command if none is given. d deletes the named files from the tape. At least one name argument must be given. This function is not permitted on magtapes. x extracts the named files from the tape to the file system. The owner and mode are restored. If no file argument is given, the entire contents of the tape are extracted. t lists the names of the specified files. If no file argument is given, the entire contents of the tape is listed. The following characters may be used in addition to the letter which selects the function desired. m Specifies magtape as opposed to DECtape. 0,...,7 This modifier selects the drive on which the tape is mounted. For DECtape, x is default; for magtape `0' is the default. v Normally tp does its work silently. The v (verbose) option causes it to type the name of each file it treats preceded by the function letter. With the t function, v gives more information about the tape entries than just the name. c means a fresh dump is being created; the tape directory is cleared before beginning. Usable only with r and u. This option is assumed with magtape since it is impossible to selectively overwrite magtape. i Errors reading and writing the tape are noted, but no action is taken. Normally, errors cause a return to the command level. f Use the first named file, rather than a tape, as the archive. This option is known to work only with x. w causes tp to pause before treating each file, type the indicative letter and the file name (as with v) and await the user's response. Response y means `yes', so the file is treated. Null response means `no', and the file does not take part in whatever is being done. Response x means `exit'; the tp command terminates immediately. In the x function, files previously asked about have been extracted already. With r, u, and d no change has been made to the tape. FILES
/dev/tap? /dev/mt? SEE ALSO
ar(1), tar(1) DIAGNOSTICS
Several; the non-obvious one is `Phase error', which means the file changed after it was selected for dumping but before it was dumped. BUGS
A single file with several links to it is treated like several files. Binary-coded control information makes magnetic tapes written by tp difficult to carry to other machines; tar(1) avoids the problem. deprecated TP(1)
All times are GMT -4. The time now is 01:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy