>-----Original Message----- >From: ataraid-list-bounces@xxxxxxxxxx [mailto:ataraid-list-bounces@xxxxxxxxxx] On Behalf Of Heinz >Mauelshagen >Sent: Friday, December 21, 2007 7:40 AM >To: ATARAID (eg, Promise Fasttrak, Highpoint 370) related discussions >Subject: Re: Adaptec HostRAID ddf1 on Supermicro X7DBR-i+ > >On Tue, Dec 18, 2007 at 04:18:55PM -0500, Phillip Susi wrote: >> Andrew Peabody wrote: >>> Hi Everyone, >>> >>> First I want to say that dmraid was been a wonderful tool for use. We use >>> it with many Sun X2100s, and other motherboards with great success. The >>> only feature we really miss is an option like mdmonitor to notify us if >>> there is a problem with an array. >> >> Currently dmraid has no error handling capability, so you probably don't >> want to use it on a server needing fault tolerance. > >This is being implemeted with the kind help of Intel >and will be released ASAP next year. I have some packages for event monitoring available, but no where to host it at the moment (no outward facing Intel site to post it too that is). I also have a number of documents I've written that help a user new to dmraid setup everything they will need to get raid array event monitoring running. :) Here is a sample of what will be reported to the syslog using these packages when an I/O error is encountered: Jan 7 06:40:55 dmraid-devhost dmeventd[3254]: Processing Raid Volume "isw_eecebgiia_raid0" for Events Jan 7 06:40:55 dmraid-devhost dmeventd[3254]: Stripe device, 8:16 (/dev/sdb) has reported an I/O error. Jan 7 06:40:55 dmraid-devhost dmeventd[3254]: The kernel has recorded 7 event(s) against this device. Jan 7 06:40:55 dmraid-devhost dmeventd[3254]: Associated Userspace Names: /dev/sdb=Disabled /dev/sdc=Active Jan 7 06:40:55 dmraid-devhost dmeventd[3254]: Associated SATA Port Mapping: /dev/sdb=2 /dev/sdc=3 Jan 7 06:40:55 dmraid-devhost dmeventd[3254]: Associated UUID: DMRAID-isw_eecebgiia_raid0 Jan 7 06:40:55 dmraid-devhost dmeventd[3254]: End of event processing for Raid Volume "isw_eecebgiia_raid0" It will tell you the specific hardware device in the raid set that is failing using three ways: the major:minor number, the associated userspace name, and finally the port number on the mainboard that the SATA device is connected to. All of this is done using kernel driver patches (Jonathan Brassow's mirror patches, Heinz Mauelshagen's raid 4/5 patch, and my raid 0 patches) along with a DSO and a registration tool that I've put together. (The utility is used to load/register the DSO with the dmeventd monitoring daemon.) I've also written special logwatch scripts to be used with this setup (for use by system admins and have documents to help with complete setup for that also). Here is a sample of what an email alert would look like when a dmraid I/O error is encountered: ################### Logwatch 7.3.4 (02/17/07) #################### Processing Initiated: Mon Jan 7 06:41:01 2008 Date Range Processed: today ( 2008-Jan-07 ) Period is day. Detail Level of Output: 5 Type of Output: unformatted Logfiles for Host: dmraid-devhost.localdomain ################################################################## --------------------- Dmeventd Errors Begin ------------------------ There were a total of 7 new log entries Date Message ------------------------ Jan 7 06:40:55: Processing Raid Volume "isw_eecebgiia_raid0" for Events Jan 7 06:40:55: Stripe device, 8:16 (/dev/sdb) has reported an I/O error. Jan 7 06:40:55: The kernel has recorded 7 event(s) against this device. Jan 7 06:40:55: Associated Userspace Names: /dev/sdb=Disabled /dev/sdc=Active Jan 7 06:40:55: Associated SATA Port Mapping: /dev/sdb=2 /dev/sdc=3 Jan 7 06:40:55: Associated UUID: DMRAID-isw_eecebgiia_raid0 Jan 7 06:40:55: End of event processing for Raid Volume "isw_eecebgiia_raid0" ---------------------- Dmeventd Errors End ------------------------- ###################### Logwatch End ######################### I'm hoping that this is something that users of dmraid will find useful. (Note: this is beta software that has had quite a bit of internal testing, but your mileage may vary out in the real world.) Thanks, Brian W. > >Heinz > >> >> _______________________________________________ >> Ataraid-list mailing list >> Ataraid-list@xxxxxxxxxx >> https://www.redhat.com/mailman/listinfo/ataraid-list > >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -=-=-=- > >Heinz Mauelshagen Red Hat GmbH >Consulting Development Engineer Am Sonnenhang 11 >Storage Development 56242 Marienrachdorf > Germany >Mauelshagen@xxxxxxxxxx PHONE +49 171 7803392 > FAX +49 2626 924446 >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -=-=-=- > >_______________________________________________ >Ataraid-list mailing list >Ataraid-list@xxxxxxxxxx >https://www.redhat.com/mailman/listinfo/ataraid-list -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
