Table of Contents
Advertisement
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
0
8
1
8
2
8
3
8
4
8
6.6.4 Monitoring a Remirror or Reconstruction
You can follow the progress of the synchronization or reconstruction process by examining the /
proc/mdstat file.
You can control the speed of synchronization by setting parameters in the /proc/sys/dev/
raid/speed_limit_min and /proc/sys/dev/raid/speed_limit_max files. To
speed up the process, echo a larger number into the speed_limit_min file.
6.6.5 Configuring mdadm to Send an E-Mail Alert for RAID
Events
You might want to configure the mdadm service to an e-mail alert for software RAID events.
Monitoring is only meaningful for RAIDs 1, 4, 5, 6, 10 or multipath arrays as 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.
The following table identifies RAID events and which events trigger e-mail alerts. All events cause
the program to be run. The program is run with two or three arguments: the event name, the array
device (such as /dev/md1), and possibly a second device. For Fail, Fail Spare, and Spare Active
the second device is the relevant component device. For MoveSpare, the second device is the array
that the spare was moved from.
Minor
RaidDevice State
97
0
113
1
129
2
145
3
161
4
active sync
/dev/sdg1
spare rebuilding
active sync
/dev/sdi1
active sync
/dev/sdj1
active sync
/dev/sdk1
Managing Software RAIDs with EVMS
/dev/sdh1
71
Advertisement
Chapters
Table of Contents
