From: Sarah Newman <srn@prgmr.com>
To: NeilBrown <nfbrown@novell.com>, linux-raid@vger.kernel.org
Subject: Re: mdadm bad blocks list
Date: Sat, 30 Jan 2016 10:22:11 -0800 [thread overview]
Message-ID: <56ACFF53.2020402@prgmr.com> (raw)
In-Reply-To: <56A99118.2080508@prgmr.com>
On 01/27/2016 07:55 PM, Sarah Newman wrote:
> On 01/27/2016 07:19 PM, NeilBrown wrote:
>> On Thu, Jan 28 2016, Sarah Newman wrote:
>>
>>> I experienced the following problems with the mdadm bad blocks list:
>>>
>>> 1. Additions to the bad block list do not cause an email to be sent by the mdadm monitor. Expected behavior is for an email to be sent as soon as the
>>> bad blocks list becomes non-empty.
>>
>> Yes, that would be a good idea. If you do develop patches, please post
>> them.
>
> Will do, but I don't have a definite time frame for it.
Since patches will not immediately propagate, I wrote an ansible role https://github.com/prgmrcom/ansible-role-mdadm-bad-blocks which contains the
script https://github.com/prgmrcom/ansible-role-mdadm-bad-blocks/blob/master/files/usr/local/bin/raid-bad-blocks . Feedback welcome.
next prev parent reply other threads:[~2016-01-30 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 18:45 mdadm bad blocks list Sarah Newman
2016-01-28 3:19 ` NeilBrown
2016-01-28 3:55 ` Sarah Newman
2016-01-28 4:45 ` NeilBrown
2016-01-30 18:22 ` Sarah Newman [this message]
2016-01-28 11:41 ` deprecating /proc/mdstat (was: Re: mdadm bad blocks list) Jens-U. Mozdzen
2016-01-28 18:21 ` Shaohua Li
2016-02-02 14:33 ` deprecating /proc/mdstat Jes Sorensen
2016-02-02 2:40 ` mdadm bad blocks list Sarah Newman
2016-02-11 4:15 ` NeilBrown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56ACFF53.2020402@prgmr.com \
--to=srn@prgmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=nfbrown@novell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).