05-08-2002
Restoring a single file...???
Can anyone please help...?
Managed to do a ufsdump of files to tape. Having trouble using ufsrestore to pull a single file back by filename??
I have dumped a single file to tape also because looking through the other threads, I noticed that you have to tell it to skip files before you get to the one you want to restore. Hope this is understandable?? Either way I just need to pull one named file back.
Thanks for helping Jonathan.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help please
i have "inherited" a Sco Server (the administrator departed in a hurry...yes we are chasing him..) and haven't used Unix for 8 years.
i have a file that i need to retrieve from a tape.
i have been able to find the file on tape using the cpio -ivt command.
however...
the problem I... (3 Replies)
Discussion started by: mfischer
3 Replies
2. Solaris
Is it possible to restore a TAR'ed file off of a tape to a location other than the original location? If so, how?
(The MAN pages give examples of how to restore only to the originating location.)
Thanks!! (1 Reply)
Discussion started by: FredSmith
1 Replies
3. UNIX for Dummies Questions & Answers
I was recently given the responsibility of the unix box at our work. Without much training, I now have to go back and restore a file from tape. I'm having some trouble with it. I'm getting an error with the blocksize.
The part of the script that does the tar looks like this:
tar cvfX... (11 Replies)
Discussion started by: citrowske
11 Replies
4. Shell Programming and Scripting
I'm new to Unix and have just wrote a little program to move files to a recycle bin (a Directory i created) and restore them. The problem is that i need to keep track of all the full filenames so that i can restore them to the right place. I did this by creating a file called delreg and putting the... (4 Replies)
Discussion started by: zoolz
4 Replies
5. Shell Programming and Scripting
Hello everyone,
I am new to unix shell.
I have a file called Path.txt....and i have data in that as
1 abhi
2 avi
3 ash so on.....
1 ,2 ,3 is the... (2 Replies)
Discussion started by: AbhijitIT
2 Replies
6. UNIX for Dummies Questions & Answers
Hello
I take a backup using the following command on Solaris 9
tar cvf /dev/rmt/0n data
the data volume contains a number of files say a, b, c , d ... etc
Now I want to restore only one file (eg b) from the data volume.
When I issue the command
tar xvf /dev/rmt/0n data/b... (1 Reply)
Discussion started by: rahmantanko
1 Replies
7. Red Hat
Post deleted. (0 Replies)
Discussion started by: Nobody_knows_me
0 Replies
8. Shell Programming and Scripting
Hello everyone,
I am attempting to make a recycling bin type application in shell script (tcsh). I have the whole part of the application done where someone can recycle files from one location to the recycling bin (the lower half of the program), this is not a problem. However I wanted to make... (7 Replies)
Discussion started by: tastybrownies
7 Replies
9. UNIX for Dummies Questions & Answers
Is there a way I could recover a deleted text file with "rm -rf" command.
Running CentOS 6.5.
Thank you. (5 Replies)
Discussion started by: galford
5 Replies
10. UNIX for Advanced & Expert Users
Quite an obscure question I think.
We have a rebuild process for remote sites that allows us to PXE rebuild a till (actually a PC with a touch screen and various fancy bits) running CentOS. The current CentOS5 tills work just fine with a tar image restore and some personalisation. Sadly,... (4 Replies)
Discussion started by: rbatte1
4 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)