DMRAID Event Processing
- Development packages
- Problem reporting
The DMRAID eventing packages supplied here give device mapper users the ability to monitor events generated by the device mapper raid kernel drivers. These packages enable event processing available for various raid levels: raid 0, raid 1, raid 4/5, and raid 10. When installed an event will be caught by the dmeventd daemon and sent for further processing within the libdmraid-events DSO. After processing an error there will be a syslog entry like the following:
- Jan 7 06:40:55 dmraid-devhost dmeventd: Processing Raid Volume "isw_eecebgiia_raid0" for Events
- Jan 7 06:40:55 dmraid-devhost dmeventd: Stripe device, 8:16 (/dev/sdb) has reported an I/O error.
- Jan 7 06:40:55 dmraid-devhost dmeventd: The kernel has recorded 7 event(s) against this device.
- Jan 7 06:40:55 dmraid-devhost dmeventd: Associated Userspace Names: /dev/sdb=Disabled /dev/sdc=Active
- Jan 7 06:40:55 dmraid-devhost dmeventd: Associated SATA Port Mapping: /dev/sdb=2 /dev/sdc=3
- Jan 7 06:40:55 dmraid-devhost dmeventd: Associated UUID: DMRAID-isw_eecebgiia_raid0
- Jan 7 06:40:55 dmraid-devhost dmeventd: End of event processing for Raid Volume "isw_eecebgiia_raid0"
Additionally, if sgpio handling is enabled in the kernel and the sgpio application installed, hdd leds will be used to indicate disk status.
There are no serious issues known to the developers at the moment but it is wise to treat this as you would any development code.
Here’s whats available:
One zip file containing a kernel driver patch for raid 4/5 enablement which can be found at the maintainers website:
Additional patch for RAID 5 events:
Tar packages packages that containing:
dmevent dmraid DSO - libdmraid-events_DSO-1.0.0.rc4.tgz
DSO registration/deregistration tool - dm_dso_reg_tool-1.0.0.rc2.tgz
Setup scripts enabling log watching - Logwatch_Dmeventd_Setup_Files.tgz
Sgpio application - sgpio-1.2.1.tgz
These "How To" are useful when setting up dmraid event monitoring:
- This is a setup guide that explains how to get dmeventd monitoring for kernel events from the ground up.
- This is a detailed guide from the ground up to get Logwatch monitoring setup for dmeventd
- And finally, a guide that gives examples of what a user of dmeventd monitoring should expect to see in their logfiles, email, and on the command line from the utilities.
Reporting Problems with DMRAID Eventing
DMRAID eventing is still under development and we appreciate your feedback and problem reports. Please send problem reports to the dm-devel & ataraid-list mailing lists, CC'ing adam.cetnerowski AT intel DOT com. When reporting bugs, please try to include the following information:
- A description of events that led up to the problem (for e.g. "unable to register a raid volume for monitoring because....")
- Any errors or messages that appeared on the terminal or in syslog at the time of the problem
- Version numbers of all the utilities used: dmraid, dm_dso_reg_tool, and device-mapper userspace tools
If we are unable to resolve your issue with this information, we may ask you to collect further details from the system to aid debugging.