09-20-2001
in HP-UX its tar tv
this shows the contents of the tape
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Does anyone know the UNIX command to view and/or erase data that is on an 8-track tape? Thanks for your help! Linda (13 Replies)
Discussion started by: lfulton
13 Replies
2. UNIX for Dummies Questions & Answers
I have a script which runs overnight to backup a database into a tar file. I then gzip the file and send it off to a tape device.
The command I'm using for the tape backup is
tar cvf /dev/rmt/0n /var/dbbackup/${FILE}.gz
I thought the n meant no rewind so the next file is copied to tape... (4 Replies)
Discussion started by: mattd
4 Replies
3. Solaris
hello everybody...
i need some help ...
so... i need to do some backups from one solaris system and i dont know whitch is the best solution....to use tar or ufsdump...?
...and .... how can i restore files from tape if on the tape i have 2 sessions....how can i access second session....?
enough... (4 Replies)
Discussion started by: nich007
4 Replies
4. UNIX for Dummies Questions & Answers
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)
Discussion started by: ayzeayem
0 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I performed backup on tape and I want to append more files to my previous backup on the same backup tape. But before I do that I need to know the backup file size of the first backup I performed so that I know the available size on the backup tape. Can someone help me what command I will use... (0 Replies)
Discussion started by: ayhanne
0 Replies
6. SCO
I am trying to make a full backup of my system using the cpio command. The Tape Unit is a SCSI DDS.
The process started fine but after about 30 minutes, it just stopped and showed the following message:
1755 Signal 31 - Core dumped
Any idea of what is causing this and how to fix it?
... (4 Replies)
Discussion started by: zionpc
4 Replies
7. UNIX for Dummies Questions & Answers
on Darwin terminal how do i do it? (0 Replies)
Discussion started by: cleansing_flame
0 Replies
8. Red Hat
I'm using tar and so far so good, but how can I view ALL files without having to fast forward and rewind the tape? Let's say I append 100 files onto the tape. Having to fast forward 100 times until I find the file I want is kinda tedious. (3 Replies)
Discussion started by: sdotsen
3 Replies
9. AIX
I have an AIX server with a tape Library residing on it. I intend to restore the data backed up to the tape on Red Hat Enterprise Linux 5.
First , i would want to view the contents of the tape on RHEL 5(x86) but seems to be giving an input output error.
I observed that if i backup to tape on... (1 Reply)
Discussion started by: optimum
1 Replies
10. UNIX for Dummies Questions & Answers
I have an AIX server with a tape Library residing on it. I intend to restore the data backed up to the tape on Red Hat Enterprise Linux 5.
First , i would want to view the contents of the tape on RHEL 5(x86) but seems to be giving an input output error.
I observed that if i backup to tape on... (20 Replies)
Discussion started by: optimum
20 Replies
tar(5) File Formats Manual tar(5)
Name
tar, mdtar - tape archive file format
Description
The tape archive command dumps several files, including special files, into one, in a medium suitable for transportation.
A tape or file is a series of blocks. Each block is of size TBLOCK. A file on the tape is represented by a header block, which describes
the file, followed by zero or more blocks, which give the contents of the file. At the end of the tape are two blocks filled with binary
zeros, as an end-of-file indicator.
The blocks are grouped for physical I/O operations. Each group of n blocks (where n is set by the option on the command line, and the
default is 20 blocks) is written with a single system call; on 9-track tapes, the result of this write is a single tape record. The last
group is always written at the full size, so blocks after the two zero blocks contain random data. On reading, the specified or default
group size is used for the first read, but if that read returns less than a full tape block, the reduced block size is used for further
reads.
The following is an example of a header block:
#define TBLOCK 512
#define NAMSIZ 100
union hblock {
char dummy[TBLOCK];
struct header {
char name[NAMSIZ];
char mode[8];
char uid[8];
char gid[8];
char size[12];
char mtime[12];
char chksum[8];
char linkflag;
char linkname[NAMSIZ];
char rdev[6]
} dbuf;
};
The name field is a null-terminated string. The other fields are 0-filled octal numbers in ASCII. Each field (of width w) contains w
minus 2 digits, a space, and a null, except size and mtime , which do not contain the trailing null. The name field specifies the name of
the file, as specified on the command line. Files dumped because they were in a directory that was named in the command line have the
directory name as prefix and /filename as suffix. The field specifies the file mode, with the top bit masked off. The uid and gid fields
specify the user and group numbers that own the file. The size field specifies the size of the file in bytes. Links and symbolic links
are dumped with this field specified as zero. The mtime field specifies the modification time of the file at the time it was dumped. The
chksum field is a decimal ASCII value, which represents the sum of all the bytes in the header block. When calculating the checksum, the
chksum field is treated as if it were all blanks. The linkflag field is ASCII 0 if the file is normal or a special file and ASCII 1 if it
is a hard link, and ASCII 2 if it is a symbolic link. The name to which it is linked, if any, is in linkname, with a trailing null.
Unused fields of the header are binary zeros and are included in the checksum. The rdev field encodes the ASCII representation of a device
special file's major and minor device numbers.
The first time a given i-node number is dumped, it is dumped as a regular file. The second and subsequent times, it is dumped as a link
instead. Upon retrieval, if a link entry is retrieved, but not the file it was linked to, an error message is printed and the tape must be
manually rescanned to retrieve the linked file.
The encoding of the header is designed to be portable across machines.
Restrictions
Names or link names longer than NAMSIZ produce error reports and cannot be dumped.
See Also
tar(1)
tar(5)