View Single Post

   
  #3 (permalink)  
Old 01-16-2008, 11:20 AM
Tom
 
Posts: n/a
Default Re: Weird missing disk fsck boot problem

On Mar 12, 12:12 pm, Darren Dunham <ddun...@redwood.taos.com> wrote:


>
> Can you post the contents of /etc/vfstab?
>


#device device mount FS fsck
mount mount
#to mount to fsck point type pass at
boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1
yes -
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/md/dsk/d5 - - swap - no -
/dev/md/dsk/d2 /dev/md/rdsk/d2 / ufs 1 no -
/dev/md/dsk/d8 /dev/md/rdsk/d8 /usr ufs 1 no -
/dev/md/dsk/d11 /dev/md/rdsk/d11 /var ufs 1
no -
#/dev/md/dsk/d14 /dev/md/rdsk/d14 /home ufs
2 yes -
swap - /tmp tmpfs - yes -
/dev/md/dsk/d28 /dev/md/rdsk/d28 /export/qa/qa-aix2
ufs 1 yes logging
#/dev/md/dsk/d29 /dev/md/rdsk/d29 /mgrbuild
ufs 1 yes -
/dev/md/dsk/d26 /dev/md/rdsk/d26 /tools ufs 1
yes -
/dev/md/dsk/d30 /dev/md/rdsk/d30 /cvsdepot ufs 1 yes logging
/dev/md/dsk/d31 /dev/md/rdsk/d31 /datasafe ufs 1 yes logging
#/dev/md/dsk/d27 /dev/md/rdsk/d27 /localcvs ufs 1 yes -


=============

metastat:

---snip-----

d31: Soft Partition
Device: c2t10d0s6
State: Okay
Size: 327155712 blocks (156 GB)
Device Start Block Dbase Reloc
c2t10d0s6 10816 No Yes

Extent Start Block Block count
0 16788034 264241152
1 339749444 62914560

d30: Soft Partition
Device: c2t10d0s6
State: Okay
Size: 75497472 blocks (36 GB)
Device Start Block Dbase Reloc
c2t10d0s6 10816 No Yes

Extent Start Block Block count
0 10817 16777216
1 281029187 58720256

Device Relocation Information:
Device Reloc Device ID
c0t10d0 Yes id1,sd@SSEAGATE_ST336704LSUN36G_3CD1LDW100002132DR 60
c0t9d0 Yes id1,sd@SSEAGATE_ST336704LSUN36G_3CD1LG0D00002132DP NZ
c0t8d0 Yes id1,sd@SSEAGATE_ST336704LSUN36G_3CD1LBTN00007129JX Z3
c0t0d0 Yes id1,sd@SSEAGATE_ST336704LSUN36G_3CD1K51900002133FL PV
c2t10d0 Yes id1,iver@w600a0b80000a5ed90000000f3d94158d


====================================

So yes, d31 and d30 are mounted in vfstab, and metastat reports them
as belonging to c2.... when in fact they are c3..... ...and it's a
mystery to me that everything still mounts okay and is up and
available???


So, should I just issue a meta command to volume manager to update
those virtual disks to point to c3.... instead of c2...??



Thanks,

Tom


Reply With Quote