Monitoring A Remirror Or Reconstruction; Configuring Mdadm To Send An E-Mail Alert For Raid Events - Novell LINUX ENTERPRISE SERVER 10 SP2 - STORAGE ADMINISTRATION GUIDE 05-15-2009 Administration Manual

mdadm -D /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Sun Apr 16 11:37:05 2006
Raid Level : raid5
Array Size : 35535360 (33.89 GiB 36.39 GB)
Device Size : 8883840 (8.47 GiB 9.10 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Apr 17 05:50:44 2006
State : clean, degraded, recovering
Active Devices : 4
Working Devices : 5
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 128K
Rebuild Status : 3% complete
UUID : 2e686e87:1eb36d02:d3914df8:db197afe
Events : 0.189
Number Major Minor
0 8 97
1 8 113
2 8 129
3 8 145
4 8 161

6.6.4 Monitoring a Remirror or Reconstruction

You can follow the progress of the synchronization or reconstruction process by examining the
file.
proc/mdstat
You can control the speed of synchronization by setting parameters in the
and
speed_limit_min /proc/sys/dev/raid/speed_limit_max
echo a larger number into the
6.6.5 Configuring mdadm to Send an E-Mail Alert for RAID
Events
You might want to configure the
Monitoring is only meaningful for RAIDs 1, 4, 5, 6, 10 or multipath arrays because only these have
missing, spare, or failed drives to monitor. RAID 0 and Linear RAIDs do not provide fault tolerance
so they have no interesting states to monitor.
RaidDevice State
0 active sync
1 spare rebuilding
2 active sync
3 active sync
4 active sync
file.
speed_limit_min
service to send an e-mail alert for software RAID events.
mdadm
/dev/sdg1
/dev/sdh1
/dev/sdi1
/dev/sdj1
/dev/sdk1
/proc/sys/dev/raid/
files. To speed up the process,
Managing Software RAIDs with EVMS
/
93