how to verify RAID configuration info on sun solaris?

[parazhang]

I have a sun fire v240 server,now I want to know whether there is a hardware based Raid or not?

And If there is hardware based Raid,how to verify its existing by using solaris command or others?

If there is a software based Raid on my server,how to verity it and know which level Raid it is

Thanks

best regards!

 

[schu]

There are two types of RAID implementation. Software and hardware.
Do you have a storage array (extra box holding disks?) e.g. A1000, A3510 etc. These storage arrays tend to be hardware RAID.
Internal disks tend to be software RAID.

Also do you know if you have volume managers on your server e.g. Vertias VM etc?

If you can give this information it would be easier for us to tell you which commands to use.

 

[parazhang]

thanks!
I don't have a storage array,so it should be soft Raid.
I use solaris 9,and use the default volume manage on it.

So how can I verify the raid level and more disks info?

Best Regards!

 

[KenCunningham]

metastat will show you your set up. metatool (with an appropriate X-windows set up) will give you more information in that regard.

 

[dandan123]

I don't think the V240 has inbuilt h/w raid. The V440 does, you can mirror 2 internal drives.

 

[kHz]

V240 does NOT have built-in hw raid.

 

[schu]

just like ken said
metastat will give you the information you want, it takes a bit of time to understand, so man metastat for information.

 

[parazhang]

Thanks all!
now I ran the metastat,and the disks are mirrored:
root@OS9:/# metastat
d9: Mirror
Submirror 0: d19
State: Okay
Submirror 1: d29
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 64648128 blocks (30 GB)

d19: Submirror of d9
State: Okay
Size: 64648128 blocks (30 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c2t1d0s3 0 No Okay Yes


d29: Submirror of d9
State: Okay
Size: 64648128 blocks (30 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t3d0s3 0 No Okay Yes


d8: Mirror
Submirror 0: d18
State: Okay
Submirror 1: d28
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 67110720 blocks (32 GB)

d18: Submirror of d8
State: Okay
Size: 67110720 blocks (32 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c2t1d0s1 0 No Okay Yes


d28: Submirror of d8
State: Okay
Size: 67110720 blocks (32 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t3d0s1 0 No Okay Yes


d7: Mirror
Submirror 0: d17
State: Okay
Submirror 1: d27
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 5250816 blocks (2.5 GB)

d17: Submirror of d7
State: Okay
Size: 5250816 blocks (2.5 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c2t1d0s0 0 No Okay Yes


d27: Submirror of d7
State: Okay
Size: 5250816 blocks (2.5 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t3d0s0 0 No Okay Yes


d4: Mirror
Submirror 0: d14
State: Okay
Submirror 1: d24
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 41945472 blocks (20 GB)

d14: Submirror of d4
State: Okay
Size: 41945472 blocks (20 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c2t0d0s4 0 No Okay Yes


d24: Submirror of d4
State: Okay
Size: 41945472 blocks (20 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t2d0s4 0 No Okay Yes


d0: Mirror
Submirror 0: d10
State: Okay
Submirror 1: d20
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 41945472 blocks (20 GB)

d10: Submirror of d0
State: Okay
Size: 41945472 blocks (20 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c2t0d0s0 0 No Okay Yes


d20: Submirror of d0
State: Okay
Size: 41945472 blocks (20 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t2d0s0 0 No Okay Yes


d3: Mirror
Submirror 0: d13
State: Okay
Submirror 1: d23
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 51022464 blocks (24 GB)

d13: Submirror of d3
State: Okay
Size: 51022464 blocks (24 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c2t0d0s3 0 No Okay Yes


d23: Submirror of d3
State: Okay
Size: 51022464 blocks (24 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t2d0s3 0 No Okay Yes


Device Relocation Information:
Device Reloc Device ID
c1t3d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZA1GSY000075303UNE
c1t2d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZ9QQZH00007522RUT8
c2t1d0 Yes id1,sd@SFUJITSU_MAT3073N_SUN72G_000512B02HNV____AAN0P5302HNV
c2t0d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZA1LVC000075303UUG
root@OS9:/#
*************************************
But when I typed df command:

root@OS9:/# df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 20G 3.7G 16G 19% /
/proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
fd 0K 0K 0K 0% /dev/fd
swap 4.9G 40K 4.9G 1% /var/run
/dev/dsk/c2t1d0s4 3.0G 801M 2.1G 27% /oradata4
/dev/dsk/c1t3d0s4 3.0G 520M 2.4G 18% /oradata5
swap 4.9G 776K 4.9G 1% /tmp
/dev/md/dsk/d3 24G 1.8G 22G 8% /home
/dev/md/dsk/d7 2.5G 1.6G 786M 69% /oradata1
/dev/md/dsk/d9 30G 2.5G 28G 9% /oradata3
/dev/md/dsk/d8 32G 17G 15G 54% /oradata2
/dev/md/dsk/d4 20G 1.9G 18G 10% /usr/local
root@OS9:/#

It seems that c2t1d0s4 and c1t3d0s4 didn't mirror,and I aslo cannot understand the following lines:

mnttab 0K 0K 0K 0% /etc/mnttab
fd 0K 0K 0K 0% /dev/fd
swap 4.9G 40K 4.9G 1% /var/run
...
swap 4.9G 776K 4.9G 1% /tmp

which partition the two swap located on?
and what's the meaning of mnttab,fd?

Best Regards!

 

[cndcadams]

parazhang;

Look at /etc/vfstab to figure out what partition swap is on.

You are correct about the below, it does not look like they were mirrored. Whoever set the configuration up did not mirror them or the filesystems were set up after original configuration and no-one mirrored them after adding to the system.

/dev/dsk/c2t1d0s4 3.0G 801M 2.1G 27% /oradata4
/dev/dsk/c1t3d0s4 3.0G 520M 2.4G 18% /oradata5

mnttab is mounted file system table

fd is drivers for floppy disks

you can do a man on both fd and mnttab for better understanding.

Also for better understanding of swap look at man mount_tmpfs.

Also found this about /var/run

/var/run is a "RAMdisk" for performance purposes, a TMPFS-mounted file system, /var/run, which provides repository for temporaty system files not needed across system reboots. (eg,for doors, sockets, process pid numbers, and other ephemera that don't need to persist through a reboot.)

when you have a large process, it can create big tmp file in /var/run

For swap have a look at:

http://www.princeton.edu/~psg/unix/solaris/troubleshoot/ram.html

metstat -p is a little easier to read, shows config.


Thanks

CA

 

[schu]

The set up seems OK apart from the /oradata4 and /oradata5 which are not mirrored.

You can see which partition swap is on using "swap -l" command. However, swap devices are normally not mirrored, as they are slower at writing and generally do not require the protection.

 

[daFranze]

usually you would mirror swap since if it is used and the disk fails your system would run a failfast/halt if it want's to access the swap

Best Regards, Franz
--
UNIX System Manager from Munich, Germany