Making sense of df -k & format verify output

I'm posting the output from two disks on my Solaris machine. The first part is the output from using the format command and then using the verify option on each disk. The last part is the output from my df -k command. I'm trying to match the partition to the filesystem/mount point. I'm assuming the disks are mirrored. Is there a command or option under format that better shows the correlation between the partition and mount point? I was also wondering why partition 0 and 2 seem to overlap as they both begin at cylinder 0?

SunOS 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Fire-V240

DISK 0

Volume name = < >
ascii name = <SUN72G cyl 14087 alt 2 hd 24 sec 424>
pcyl = 14089
ncyl = 14087
acyl = 2
nhead = 24
nsect = 424
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 402 1.96GB (403/0/0) 4100928
1 swap wu 403 - 1610 5.86GB (1208/0/0) 12292608
2 backup wm 0 - 14086 68.35GB (14087/0/0) 143349312
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 1611 - 4026 11.72GB (2416/0/0) 24585216
7 unassigned wm 4027 - 4052 129.19MB (26/0/0) 264576

DISK 1

Volume name = < >
ascii name = <SUN72G cyl 14087 alt 2 hd 24 sec 424>
pcyl = 14089
ncyl = 14087
acyl = 2
nhead = 24
nsect = 424
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 403 1.96GB (404/0/0) 4111104
1 swap wu 404 - 1611 5.86GB (1208/0/0) 12292608
2 backup wm 0 - 14086 68.35GB (14087/0/0) 143349312
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 1612 - 4027 11.72GB (2416/0/0) 24585216

root@lycincs2:/dev/dsk# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d2 1988887 1683711 245510 88% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
swap 7895704 16 7895688 1% /var/run
swap 7906016 10328 7895688 1% /tmp
/dev/md/dsk/d8 12106732 5296345 6689320 45% /opt

Section 2 is always the entire disk. Use "metastat d2" to learn about metadisk d2. You're right, probably a mirror.

okay. I did a man page on metastat. I don't think that is exactly what I'm looking for. I have an HP-UX back ground and I'm used to the bdf command. You can easliy see the volume group and logical volume with the mount point also displayed. Is there anything in Solaris more like this output? Or how do I determine what partition the filesystem column is referring to in the df -k output?

bdf example -
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 143360 76148 63228 55% /
/dev/vg00/lvol1 83733 32180 43179 43% /stand
/dev/vg00/lvol8 1024000 190046 786033 19% /var
/dev/vg00/lvol7 1126400 1059420 63042 94% /usr
/dev/vg00/lvol4 204800 92209 105671 47% /tmp
/dev/vg00/lvol6 1740800 1624243 109311 94% /opt
/dev/vg00/lvol5 1024000 373578 610462 38% /home

df -k example -
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d2 1988887 1683951 245270 88% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
swap 7897920 16 7897904 1% /var/run
swap 7908232 10328 7897904 1% /tmp
/dev/md/dsk/d8 12106732 5286889 6698776 45% /opt

Solaris is not HP-UX and DiskSuite is not LVM. "metastat d2" will tell you all there is to know about d2. Try that command.

I did the metastat d2 command. It still doesn't help me understand the correlation between partition/slice and mount point. It seems to deal with the mirroring aspect, which is great to know. And I understand that Solaris isn't like HP-UX, I was just using that to show my point and the information I was looking for.

Here's the output from metastat -
d2: Mirror
Submirror 0: d0
State: Okay
Submirror 1: d1
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4100928 blocks

d0: Submirror of d2
State: Okay
Size: 4100928 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Okay

d1: Submirror of d2
State: Okay
Size: 4111104 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Okay

Well
/dev/dsk/c1t0d0s0 is d0
/dev/dsk/c1t1d0s0 is d1

d0 and d1 were combined to make d2

c1t1d0s0 is slice 0 that's what the s0 means.

What else are you looking for?

Something that might say
Partition/slice | size | mount point
c1t1d0s0 GB or MB /
c1t1d0s1 GB or MB /var
etc., etc...

so what's wrong with your "df -k" ? you could use "df -h" to see an human output but your mirror is mounted not the single slices.... that's the sense of the solaris volume manager......
/dev/md/dsk/d2, like Perderabo, said contains to same slices d0 and d1 which is c1t0d0s0 and c1t1d0s0 .....

I guess the mirror part is why I'm confused. I've never dealt with mirrored disks like this. So according to the output I've already listed here. Only slice 0 is mirrored on this machine? Or is it the entire disk (all slices)?

you would have to post the output of "metastat". you get the definition of every mirror in your maschine without any option..... but as far as i can see now at your df -k output the "/" and "/opt" is based on metadevices.....

Here's the output of metastat d2 - looks like d2 is a mirror of slice 0 and d8 is a mirror of slice 6. Am I correct?

root@lycincs2:/# metastat d2
d2: Mirror
Submirror 0: d0
State: Okay
Submirror 1: d1
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4100928 blocks

d0: Submirror of d2
State: Okay
Size: 4100928 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Okay

d1: Submirror of d2
State: Okay
Size: 4111104 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Okay

And metastat d8 -

root@lycincs2:/# metastat d8
d8: Mirror
Submirror 0: d6
State: Okay
Submirror 1: d7
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 24585216 blocks

d6: Submirror of d8
State: Okay
Size: 24585216 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s6 0 No Okay

d7: Submirror of d8
State: Okay
Size: 24585216 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s6 0 No Okay

I've been working with HP-UX for a long time. I have never seen anything like that. Here is the bdf output from two different HP-UX systems:

Filesystem          kbytes    used   avail %used Mounted on
/dev/vg00/lvol3     204800  106448   97640   52% /
/dev/vg00/lvol1     298928   61480  207552   23% /stand
/dev/vg00/lvol8    4710400 1324552 3362776   28% /var
/dev/vg00/lvol7    3145728 1694752 1439696   54% /usr
/dev/vg00/lvol6    1048576  402376  641168   39% /tmp
/dev/vg00/lvol5    8388608 5357120 3007912   64% /opt
/dev/vg00/lvol4    6291456 2420010 3630283   40% /export1

Filesystem          kbytes    used   avail %used Mounted on
/dev/vg00/lvol3     204800   90216  113704   44% /
/dev/vg00/lvol1     298928   49144  219888   18% /stand
/dev/vg00/lvol8    4710400  557232 4121312   12% /var
/dev/vg00/lvol7    2916352 1259240 1644832   43% /usr
/dev/vg00/lvol4     204800   25128  178464   12% /tmp
/dev/vg00/lvol6    1720320 1380704  337000   80% /opt

Can you tell me anything at all about the physical disks involved? One of the system has MirrorDisk/UX installed; and on that system, vg00 is mirrored. Which system? The HP-UX /dev/vg00/lvol1 and the SunOS /dev/md/dsk/d2 are actually rather close in concept. In both cases you need another command to trace back to the physical disk. Now looking at the SunOS "df -k" output...

Filesystem            kbytes    used   avail capacity  Mounted on
/dev/md/dsk/d0        493688   50002  394318    12%    /
/dev/md/dsk/d4       1133429  584244  492514    55%    /usr
/proc                      0       0       0     0%    /proc
fd                         0       0       0     0%    /dev/fd
mnttab                     0       0       0     0%    /etc/mnttab
/dev/md/dsk/d5       1527116  670262  795770    46%    /var
swap                 2903888      40 2903848     1%    /var/run
swap                 2903912      64 2903848     1%    /tmp
/dev/md/dsk/d8       17403836 16214482 1015316    95%    /worldscope
/dev/md/dsk/d7       2622176 1864275  705458    73%    /export
/dev/md/dsk/d6        736904    3430  674522     1%    /opt

the main difference that strikes me is "capacity" verses "%used".

I'm not sure I understood all your questions for me from the last reply. I do agree that that df -k and bdf are very simular, I was just confused by the mirroring and why some of the system type info is list the way it is. Could you explain one last point for me...
I see that /proc, fd, mnttab & swap are listed in the df -k. And I can see that /proc, fd & mnttab don't actually have any space allocated to them. I know that mnttab is used by the system to keep track of mount points. What is the purpose of /proc & fd? And why does swap have two listings and mounted at /var/run & /tmp?
thanks guys!!

/tmp and /var/run are swap-based filesystems. Anything in them will disappear at reboot time. They are like "memory-disk" filesystems, except that they use vitrual memory rather than physical memory. Putting stuff in /tmp or /var/run consumes some swap space. The proc, fd, and mnttab are psuedo filesystem they don't count as disk space at all. /proc is all of the processes. ps runs by looking at it. /dev/fd lets you treat your file descriptors as if they were files. mnttab is a file system that exists only for /etc/mnttab... not my favorite idea, but /etc/mnttab is *alway* in sync with the kernel table.