G'day all,
Here is an interesting question( well I think so in any case ). I just replaced a failed disk in my
15 drive Raid-6.
Simply mdadm --add /dev/md0 /dev/sdl
Why, when there is no other activity on the array at all, is it writing to every disk during the
recovery? I would have
Brad Campbell wrote:
G'day all,
Here is an interesting question( well I think so in any case ). I just
replaced a failed disk in my 15 drive Raid-6.
Forgot the most important detail (as usual)
bklaptop:~ssh storage1 uname -a
Linux storage1 2.6.11.7 #4 Fri Oct 7 20:00:25 GST 2005 i686
Hi Neil,
I recently setup mdadm to monitor my md RAIDs and text message my
cellphone in the event of a device failure. I found that the reports
were too verbose to easily read on my phone.
--textmsg, -T makes the emails mdadm generates shorter to be read on
mobile devices.
--
Ross Vandegrift
Hi Neil,
While adding the text message mode, I saw a FIXME asking for syslog
support in monitor mode.
This patch adds exactly that.
--
Ross Vandegrift
[EMAIL PROTECTED]
The good Christian should beware of mathematicians, and all those who
make empty prophecies. The danger already exists that
Hi Neil,
After implementing syslogging, I noticed that mdadm was logging INFO
level messages that my arrays were missing spares. Thing is, none of
my arrays have spares.
This patch adds a check for expected_spares != UnSet, so if spares=0
is missing from an array, it is not logged.
--
Ross