Talking about the SVM of Solaris with a nagios alarm

Today's OPS, most of the Linux LVM, estimated that few people understand the Solaris SVM. N years ago, in the Linux x86 has not been male, in fact, Aix/hp/sun three mainframe giants have their own set of storage management mechanisms and software, of which Sun is SVM. In addition to their own dedicated storage management software, there are third-party commercial storage management software, such as Veritas, can also be used to manage Solaris storage, but these commercial software, under the impact of today's open-source products, the days are far less than the previous scenery.

OK, nonsense. See a Nagios alert:

Messages.0:jul 15:06:41 apps2 md_mirror: [ID 104909 kern.warning] WARNING:md:d16: (unavailable) needs maintenance

This is a machine's disk is broken, what is D16 mean?

Further enquiries:

#metastat
D6:mirror
Submirror 0:d16
State:needs Maintenance
Submirror 1:d26
State:okay
Pass:1
Read Option:roundrobin (default)
Write Option:parallel (default)
size:142606464 Blocks (GB)

D16:submirror of D6
State:needs Maintenance
Invoke:metareplace d6 c1t2d0s0 <new device>
size:142606464 Blocks (GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
C1t2d0s0 0 No Maintenance Yes


D26:submirror of D6
State:okay
size:142606464 Blocks (GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
C1t3d0s0 0 No Okay Yes

Here can be clearly seen, D16 is a logical volume D6 of a mirror disk, the disk number is c1t2d0, this is very clear, c1t2d0 this plate hung, need to be replaced.

If you want to query the mirror disk information of the logical volume under the current system more clearly, there is a command:

#metastat-C
D6 m 68GB d16 (maint) d26
D16 s 68GB c1t2d0s0 (maint)
D26 s 68GB c1t3d0s0
D4 m 14GB D14 d24
D14 s 14GB c1t0d0s4
D24 s 14GB c1t1d0s4
D3 m 5.0GB D13 D23
D13 s 5.0GB c1t0d0s3
D23 s 5.0GB c1t1d0s3
D1 m 15GB D11 D21
D11 s 15GB c1t0d0s1
D21 s 15GB c1t1d0s1
D0 m 10GB D10 d20
D10 s 10GB c1t0d0s0
d20 S 10GB c1t1d0s0
D5 m 22GB D15 D25
D15 s 22GB c1t0d0s5
D25 s 22GB c1t1d0s5

The correspondence between the logical volume and the mirror disk can be seen more clearly here. In addition, the logical volume name has the corresponding entry in the/dev/md/dsk directory of the block device and the/dev/md/rdsk directory of the original device.

Contact maintenance manufacturers to change the disk can be, health status as follows:

#metastat
D6:mirror
Submirror 0:d16
State:okay
Submirror 1:d26
State:okay
Pass:1
Read Option:roundrobin (default)
Write Option:parallel (default)
size:142606464 Blocks (GB)

D16:submirror of D6
State:okay
size:142606464 Blocks (GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
C1t2d0s0 0 No Okay Yes


D26:submirror of D6
State:okay
size:142606464 Blocks (GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
C1t3d0s0 0 No Okay Yes

Note:

If the new project erection is too troublesome to use SVM, but also to do the mirror, you can directly to the new server's internal hard disk raid, the method is as follows, in OK State:

{0} OK 9 b create-raid1-volume

Build RAID1 with target 9 and Target B two disks

Refer to Oracle's official documentation for specific details.

This article is from the "Memory Fragments" blog, so be sure to keep this source http://weikle.blog.51cto.com/3324327/1681474

Talking about the SVM of Solaris with a nagios alarm