08-03-2006
When i run tar once i get the following message.
Tar: tape blocksize error
Thanks in advance,
bubeshj
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Trying to answer a question about whether tar table-of-contents is a good tool for verifying tape data. (1 Reply)
Discussion started by: tjlst15
1 Replies
2. UNIX for Dummies Questions & Answers
I downloaded what I thought was a gziped file (at least on remote server it had a .gz extention) and once I had it it was filename.tar.tar..I tried the standard untar tar -xvf filename on it and get an error. Does anyone know what's going on? (5 Replies)
Discussion started by: capeme
5 Replies
3. UNIX for Advanced & Expert Users
Hi,
On my Unix Server in my directory, I have 70 files distributed in the following directories (which have several other files too). These files include C Source Files, Shell Script Source Files, Binary Files, Object Files.
a) /usr/users/oracle/bin
b) /usr/users/oracle... (1 Reply)
Discussion started by: marconi
1 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
4 files are returned when i issue 'find . -mtime -1 -type f -ls'.
./ora_475244.aud
./ora_671958.aud
./ora_934052.aud
./ora_934050.aud
However, when I issued the below command:
tar -cvf test.tar `find . -mtime -1 -type f`, the tar file only contains the 1st file -... (2 Replies)
Discussion started by: ahSher
2 Replies
5. Shell Programming and Scripting
HI,
if I have a tarfile called pmapdata.tar that contains
tar -tvf pmapdata.tar
-rw-r--r-- 0/0 21 Oct 15 11:00 2009 /var/tmp/pmapdata/pmap4628.txt
-rw-r--r-- 0/0 21 Oct 14 20:00 2009 /var/tmp/pmapdata/pmap23752.txt
-rw-r--r-- 0/0 1625 Oct 13 20:00 2009... (1 Reply)
Discussion started by: borderblaster
1 Replies
6. Shell Programming and Scripting
Hi all,
I have a tar file and inside that tar file is a folder with additional tar.gz files. What I want to do is look inside the first tar file and then find the second tar file I'm looking for, look inside that tar.gz file to find a certain directory. I'm encountering issues by trying to... (1 Reply)
Discussion started by: bashnewbee
1 Replies
7. Shell Programming and Scripting
I have written a below script to untar the tar files from /tmp/tarfiles/ directory.
# cat /tmp/tarfiles/script.sh
#!/bin/sh
cd /tmp/tarfiles/
TFL="tar_files_list.txt"
TCF="tar_completed_list.txt"
ls -l *.tar | awk '{print $9}' > $TFL
for i in `cat $TFL`
do
if
then
for j in... (2 Replies)
Discussion started by: thomasraj87
2 Replies
8. UNIX for Dummies Questions & Answers
I would like to confirm my file.tar is been tar-ed correctly before I remove them. But I have very limited disc space to untar it.
Can I just do the listing instead of actual extract it? Can I say confirm folder integrity if the listing is sucessful without problem?
tar tvf file1.tar
... (1 Reply)
Discussion started by: vivien_chu
1 Replies
9. AIX
Coming from this thread, just wondering if there is an option to check if the Tar of the files/directory will be without any file-errors without actually making the tar.
Scenario:
Let's say you have a directory of 20GB, but you don't have the space to make Tar file at the moment, and you want... (14 Replies)
Discussion started by: filosophizer
14 Replies
TAR(5) File Formats Manual TAR(5)
NAME
tar - tape archive file format
DESCRIPTION
Tar, (the tape archive command) dumps several files into one, in a medium suitable for transportation.
A ``tar 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 b keyletter on the tar(1) command line
-- default is 20 blocks) is written with a single system call; on nine-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 header block looks like:
#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];
} dbuf;
};
Name is a null-terminated string. The other fields are zero-filled octal numbers in ASCII. Each field (of width w) contains w-2 digits, a
space, and a null, except size and mtime, which do not contain the trailing null and chksum which has a null followed by a space. Name is
the name of the file, as specified on the tar command line. Files dumped because they were in a directory which was named in the command
line have the directory name as prefix and /filename as suffix. Mode is the file mode, with the top bit masked off. Uid and gid are the
user and group numbers which own the file. Size is the size of the file in bytes. Links and symbolic links are dumped with this field
specified as zero. Mtime is the modification time of the file at the time it was dumped. Chksum is an octal 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. Link-
flag is NULL if the file is ``normal'' or a special file, ASCII `1' if it is an hard link, and ASCII `2' if it is a symbolic link. The
name linked-to, if any, is in linkname, with a trailing null. Unused fields of the header are binary zeros (and are included in the check-
sum).
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 re-scanned to retrieve the linked-to file.
The encoding of the header is designed to be portable across machines.
SEE ALSO
tar(1)
BUGS
Names or linknames longer than NAMSIZ produce error reports and cannot be dumped.
4.2 Berkeley Distribution November 7, 1985 TAR(5)