Re: mdadm never notify, grub cause fault

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday May 19, lfarkas@bnap.hu wrote:
> > 
> > I'm thinking of causing the "NewArray" alert to 
> >  - be generate for all arrays at start time
> >  - contain an indication of whether the array is degraded
> >  - cause email to be sent if the array is degraded.
> > 
> > Thus you will get an alert of a failed drive when the mdadm --monitor
> > is started.
> 
> the above are generated every every time when --monitor started? that 
> would be nice!

Yep, and it's done.

There is a patch under 

http://www.cse.unsw.edu.au/~neilb/source/mdadm/

(see 'patch' and the 'applied')

that
  1/ When mdadm --monitor first notices an array, it will check if it
  is degraded and will issue a "DegradedArray" event if it is.
  2/ mdadm --monitor has a --oneshot option which causes it to check
  once and exit. This can be used in a cron script to generate
  DegradedArray  events on a regular basis for any degraded arrays. 

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux