11-13-2014
gzcat manfucture.today.tar.gz | tar xvf -
x manfucture.today1. , 2329 bytes, 5 tape blocks
x manfucture.today2, 8090444 bytes, 15802 tape blocks
x manfucture.today3, 1714 bytes, 4 tape blocks
x manfucture.today4, 248416 bytes, 486 tape blocks
its on getting exited . do I need to interrupt I am waiting for long time to complete it.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
During tar, the command used is
tar cvf - * | remsh system_name dd of=/dev/rmt/0m bs=10k
To untar all, we used
remsh system_name "dd if=/dev/rmt/0m ibs=10k" | tar xvf -
Question?
How to untar a specific file from remote?
Thanks alot... (2 Replies)
Discussion started by: gelbvonn
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I want to UNTAR a TAR file at different location. Is it possible?
My TAR file contains the files with absolute path.
Malay (5 Replies)
Discussion started by: malaymaru
5 Replies
3. UNIX for Dummies Questions & Answers
I have file1.tar and want to untar it under /server/file2.
If I do tar -xvf file1.tar, the files will be deployed under file1.
How to specify the destination folder??
thx (3 Replies)
Discussion started by: melanie_pfefer
3 Replies
4. UNIX and Linux Applications
Hi frens,
I have to install samba on UNIX box
for that i have downloaded the samba file from netand now trying to untar that file and getting following error:
# tar -xvf samba-3.0.28a.tar.gz
UX:tar: ERROR: Directory checksum error
even i checked many times by again downloading the file... (6 Replies)
Discussion started by: NIMISH AGARWAL
6 Replies
5. UNIX for Advanced & Expert Users
Hi All,
How do I untar (tar xvf) a file through an ssh session?
I have a tar file with "relative path names".
I scp the file to a remote host:/tmp - no prob.
But when I untar the file through ssh from a remote host
it puts it in my "home directory" under the relative path -
not in /tmp... (3 Replies)
Discussion started by: Joe McCaughan
3 Replies
6. Shell Programming and Scripting
I am trying to put together a script that will check for the latest file in a directory then extract it. The extraction and the scheduling I can do, but am not sure how to get it to check for the latest file.
These files are uploaded every evening by an external party and the previous days files... (3 Replies)
Discussion started by: stheologo
3 Replies
7. UNIX for Dummies Questions & Answers
how can I untar a file without extracting it?
sample: file.tar to file
thanks,
lara (1 Reply)
Discussion started by: lhareigh890
1 Replies
8. UNIX for Dummies Questions & Answers
I have a tar file that I need to extract a single file to the current directory. The file I want to extract is located in the tar at the following path inside the tar file: repository/parts/SDCG.tgz
I use the following command to extract the file:
tar xf delivery.tar... (2 Replies)
Discussion started by: rpinsky
2 Replies
9. Shell Programming and Scripting
Hello Experts,
I have requirement in which a file is present in the folder_test. In that folder there is file called Test.tar.gz.20111102. Now my requirement is i have to rename this file to someother format and untar it....
folder_test
Test.tar.gz.20111102
I am using the below... (5 Replies)
Discussion started by: aks_1902
5 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I have been trying to untar this file hello.tar which consists of 3 files but nothing happens:
eux750{root}# tar -xvf hello.tar
x /hello, 8405 bytes, 17 tape blocks
Why am I not able to see the untarred files.:wall:
Thanks to help! (2 Replies)
Discussion started by: terminator
2 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)