06-16-2011
Perhaps. It depends on how you ran tar, but maybe: tar -C /path/to/whereImounted -xf /path/to/tapedev /etc which should extract /etc from the tape and put it into /path/to/whereImounted
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello!
When I use "sar -d" I get information about disk activities like:
sd0 ...
sd0,a ...
sd0,b ...
.....
sd22 ...
sd22,a ...
.....
How I can find by , for example sd22,a , what physical disk is it. For example /dev/dsk/c1t3d0s1 easy to read and I can find by it physical disk.... (4 Replies)
Discussion started by: Colf
4 Replies
2. Solaris
I've searched through unix.com and google for this issue I am having on one particular Sun E280R with installing netbackup software from CD. I know the cd is good because i installed the software on 4 other servers right before this one.
This is the issue I am seeing. vold does not mount the CD... (2 Replies)
Discussion started by: dangral
2 Replies
3. Solaris
I use the following command dk -k and get the following output:
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 1587078 56546 1482920 4% /
/dev/dsk/c0t0d0s6 1984230 926199 998505 49% /usr
/proc 0 0 0 ... (1 Reply)
Discussion started by: indianboy08
1 Replies
4. Solaris
Hi all,
I just find some strange device (at least to me) on my Sun Blade server, CP3060, like below:
bash-3.00# cd /dev/dsk
bash-3.00# ls c3*
c3t600A0B80002FA5F50000000000000000d0s0 c3t600A0B80002FA60C0000000000000000d0s4
c3t600A0B80002FA5F50000000000000000d0s1 ... (6 Replies)
Discussion started by: sleepy_11
6 Replies
5. Solaris
Hi,
I need to fsck the root file system on my Solaris 9 server. It is a UFS file system but it is under Veritas control. I want to know which fsck I need to use to check the file system. The default Solaris fsck (/usr/sbin/fsck) or the Veritas (/lib/fs/vxfs/sparcv9/fsck) fsck? I take it I... (3 Replies)
Discussion started by: gwhelan
3 Replies
6. Solaris
I have a Solaris machine running OpenSolaris v5.11.
It came with a hard drive. It's called /dev/dsk/c4d0s0.
I added two new hard drives into the box. I can't figure out what it's called in /dev/dsk. There are 210 filenames in /dev/dsk.
How do I find out which filename corresponds to the... (2 Replies)
Discussion started by: sqa777
2 Replies
7. Solaris
how to make less capacity on /dev/dsk/c1t0d0s5
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 9.6G 2.3G 7.2G 25% /
/dev/dsk/c1t0d0s1 9.6G 4.1G 5.4G 44% /usr
/dev/dsk/c1t0d0s4 9.6G 81M 9.4G 1% /var... (1 Reply)
Discussion started by: Cah.Lanang
1 Replies
8. Solaris
Our used size is 83 gb. Total of the folders and documents size is46,2 gb. 83-46=37 gb.
Where is my space. Where was lost?
Could you please I need your opinions?
{root}/space>du -s -h *
308K alaerrm-jprof
1K argerela
20G baerckup_in
1.8G cererm
28M ecerlipselink
... (8 Replies)
Discussion started by: getrue
8 Replies
9. Solaris
Hello friends,
I Working with Solaris 8 on a SunFireV890, 150 GB SCSI HD's in Raid 1 (mirroring), my problem is that the master disk failed and going to put the slave (mirror) as a Master in the slot 0 (SCSI) will not start.
The original mounting this, mirror in Raid 0:
c1t0d0s0 (master)... (10 Replies)
Discussion started by: grymorum
10 Replies
10. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
tar(4) Kernel Interfaces Manual tar(4)
NAME
tar - format of tar tape archive
DESCRIPTION
The header structure produced by (see tar(1)) is as follows (the array size defined by the constants is shown on the right):
All characters are represented in ASCII. There is no padding used in the header block; all fields are contiguous.
The fields magic, uname, and gname are null-terminated character strings. The fields name, linkname, and prefix are null-terminated char-
acter strings except when all characters in the array contain non-null characters, including the last character. The version field is two
bytes containing the characters (zero-zero). The typeflag contains a single character. All other fields are leading-zero-filled octal
numbers in ASCII. Each numeric field is terminated by one or more space or null characters.
The name and the prefix fields produce the pathname of the file. The hierarchical relationship of the file is retained by specifying the
pathname as a path prefix, with a slash character and filename as the suffix. If the prefix contains non-null characters, prefix, a slash
character, and name are concatenated without modification or addition of new characters to produce a new pathname. In this manner, path-
names of at most 256 characters can be supported. If a pathname does not fit in the space provided, the format-creating utility notifies
the user of the error, and no attempt is made to store any part of the file, header, or data on the medium.
SEE ALSO
tar(1)
STANDARDS CONFORMANCE
tar(4)