Solaris Volume Manager (SVM) issue with mirroring the disks.

Gurus,
I just installed Solaris 10 05/08 on the server. I created state database on slice 3 and 4 on two disk c0t0d0 and c0t1d0. I created two slices 6 and 7 with about 1gb space and 500mb on each slice. I used the following command.
metainit d51 1 1 c0t0d0s3
metainit d52 1 1 c0t1d0s3
metainit d5 -m d51
metattach d5 d52
and same process for d6 mirror.
I manually tried to mount and I can mount it and I can see the content on c0t0d0s3 with the following mount command
mount /dev/md/dsk/d6 /sam but when I unmount and add entry into vfstab and do mountall it does not mount the mount point /sam. I added entry on vfstab and rebooted the server without any problem but it didn't mount the filesystem. Again if I manually mount then I can mount and see the content on the disk. Here is detail from the server. I really appreciate if someone please guide if I am missing something or is there any bug on the system or need to upgrade or apply any patches.
Thanks
- KS
# uname -a
SunOS samrat 5.10 Generic_127127-11 sun4u sparc SUNW,UltraSPARC-IIi-cEngine
#
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 20169850 13690434 6277718 69% /
/devices 0 0 0 0% /devices
ctfs 0 0 0 0% /system/contract
proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
swap 2824016 1472 2822544 1% /etc/svc/volatile
objfs 0 0 0 0% /system/object
fd 0 0 0 0% /dev/fd
swap 2822544 0 2822544 0% /tmp
swap 2822584 40 2822544 1% /var/run
#
------------------------------------------------------------------
# more /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0t0d0s1 - - swap - no -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no -
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
/dev/md/dsk/d6 /dev/md/rdsk/d6 /sam ufs 1 no logging
/dev/md/dsk/d5 /dev/md/rdsk/d5 /cisco ufs 1 no logging
swap - /tmp tmpfs - yes -

I even move swap on top up /sam and also tried moving bottom but didn't work.
----------------------------------------------------
# mountall
mount: /tmp is already mounted or swap is busy
#

# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 20169850 13690434 6277718 69% /
/devices 0 0 0 0% /devices
ctfs 0 0 0 0% /system/contract
proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
swap 2824184 1472 2822712 1% /etc/svc/volatile
objfs 0 0 0 0% /system/object
fd 0 0 0 0% /dev/fd
swap 2822712 0 2822712 0% /tmp
swap 2822752 40 2822712 1% /var/run
#

# metastat |more
d6: Mirror
Submirror 0: d61
State: Okay
Submirror 1: d62
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 1025595 blocks (500 MB)
d61: Submirror of d6
State: Okay
Size: 1025595 blocks (500 MB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c0t1d0s7 0 No Okay Yes

d62: Submirror of d6
State: Okay
Size: 1025595 blocks (500 MB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c0t0d0s7 0 No Okay Yes

d5: Mirror
Submirror 0: d51
State: Okay
Submirror 1: d52
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 2097414 blocks (1.0 GB)
d51: Submirror of d5
State: Okay
Size: 2097414 blocks (1.0 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c0t0d0s6 0 No Okay Yes

d52: Submirror of d5
State: Okay
Size: 6110235 blocks (2.9 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c0t1d0s6 0 No Okay Yes

Device Relocation Information:
Device Reloc Device ID
c0t0d0 Yes id1,sd@SSEAGATE_ST336704LSUN36G_3CD1XFL600007141DJ82
c0t1d0 Yes id1,sd@SSEAGATE_ST336704LSUN36G_3CD1AK9W00007125L64L
-------------------------------------------------
# metadb
flags first blk block count
a m pc luo 16 8192 /dev/dsk/c0t0d0s3
a pc luo 16 8192 /dev/dsk/c0t0d0s4
a pc luo 16 8192 /dev/dsk/c0t1d0s3
a pc luo 16 8192 /dev/dsk/c0t1d0s4
#

# mount /dev/md/dsk/d6 /sam
# mount /dev/md/dsk/d5 /cisco

# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 20169850 13690434 6277718 69% /
/devices 0 0 0 0% /devices
ctfs 0 0 0 0% /system/contract
proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
swap 2823512 1472 2822040 1% /etc/svc/volatile
objfs 0 0 0 0% /system/object
fd 0 0 0 0% /dev/fd
swap 2822040 0 2822040 0% /tmp
swap 2822080 40 2822040 1% /var/run
/dev/md/dsk/d6 482308 1252 432826 1% /sam
/dev/md/dsk/d5 1016306 1252 954076 1% /cisco
#
_______________________________________________
sunmanagers mailing list
sunmanagers@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

Relevant Pages

  • Re: SVM: From metadevice to non-metadevice and back to metadevice
    ... > mirrors and mount it as a normal ufs file system and do some changes ... > then you mirror it back you should be able to get the data back on both ... going ON the submirror or directly at the raw disk as I think you indicated. ...
    (comp.unix.solaris)
  • Backing off mirror of / in Solaris Disk Suite
    ... / had been mirrored on 2 systems and I need to back off the mirror. ... d9: Submirror of d98 ... As the system could not mount /, we decide to mount / into ...
    (comp.unix.solaris)
  • Upgrade Solaris 9 with SVM Question
    ... d8: Mirror ... Submirror 0: d18 ... Stripe 0: ... o - replica active prior to last mddb configuration change ...
    (SunManagers)
  • Re: backing up mirrored root
    ... I had assumed an implicit sync in there. ... has no knowledge of what might be stored on the submirror. ... > normal hardware fault, sync up the mirror again, and restart the backup. ... > secondary submirror was taken offline. ...
    (comp.unix.solaris)
  • SUMMARY : Updating a mirror metadevice size
    ... Some suggested using growfs but the problem was on the metadevice mirror ... underlying submirrors, and yes it worked, the mirror size has been updated. ... Grow the partition under the detached/cleared submirror (format) ...
    (SunManagers)