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.
thanks. what does the applied means? I'm just check both the tgz and rpms but it seems to me that are older. I always prefere the release like 1.2.1 what's more if an rpm would be supplied:-))
thnaks.
-- Levente "Si vis pacem para bellum!"
- 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
