From: Tomasz Majchrzak <tomasz.majchrzak@intel.com>
To: linux-raid@vger.kernel.org
Cc: shli@kernel.org, Jes.Sorensen@redhat.com, jes.sorensen@gmail.com,
Tomasz Majchrzak <tomasz.majchrzak@intel.com>
Subject: [PATCH 0/2] Bad block notification
Date: Tue, 24 Jan 2017 13:03:37 +0100 [thread overview]
Message-ID: <1485259419-2308-1-git-send-email-tomasz.majchrzak@intel.com> (raw)
At the moment there is no way to be notified that bad blocks have been found on
a disk. It is only possible to check manually with 'mdadm --examine-badblocks'.
User might not be aware there is a bad block for a long period. If another disk
in the array fails, data is lost.
These patches add a new event to the kernel and mdadm in order to send
notification on the first bad block on a disk. I have chosen to do it only for
first bad block as I think it's sufficient indication that the drive requires
replacement.
Tomasz Majchrzak (1):
md: add bad block flag to disk state
drivers/md/md.c | 2 ++
include/uapi/linux/raid/md_p.h | 1 +
2 files changed, 3 insertions(+)
Tomasz Majchrzak (1):
Monitor: add new event BadBlocks
Monitor.c | 14 +++++++++-----
md_p.h | 1 +
mdadm.8.in | 10 ++++++++--
3 files changed, 18 insertions(+), 7 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-01-24 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 12:03 Tomasz Majchrzak [this message]
2017-01-24 12:03 ` [PATCH 1/2] md: add bad block flag to disk state Tomasz Majchrzak
2017-01-30 23:33 ` Shaohua Li
2017-02-01 9:53 ` Tomasz Majchrzak
2017-02-01 18:12 ` Shaohua Li
2017-03-06 20:23 ` jes.sorensen
2017-03-07 6:54 ` Hannes Reinecke
2017-01-24 12:03 ` [PATCH 2/2] Monitor: add new event BadBlocks Tomasz Majchrzak
2017-01-29 17:44 ` [PATCH 0/2] Bad block notification jes.sorensen
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=1485259419-2308-1-git-send-email-tomasz.majchrzak@intel.com \
--to=tomasz.majchrzak@intel.com \
--cc=Jes.Sorensen@redhat.com \
--cc=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
/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).