From: Jes Sorensen <jes.sorensen@gmail.com>
To: Tomasz Majchrzak <tomasz.majchrzak@intel.com>,
linux-raid@vger.kernel.org
Subject: Re: [PATCH] Get failed disk count from array state
Date: Fri, 19 May 2017 15:43:07 -0400 [thread overview]
Message-ID: <bc4470f4-20bf-c45a-9d96-385e4b46e1e3@gmail.com> (raw)
In-Reply-To: <1494850636-28438-1-git-send-email-tomasz.majchrzak@intel.com>
On 05/15/2017 08:17 AM, Tomasz Majchrzak wrote:
> Recent commit has changed the way failed disks are counted. It breaks
> recovery for external metadata arrays as failed disks are not part of
> the array and have no corresponding entries is sysfs (they are only
> reported for containers) so degraded arrays show no failed disks.
>
> Recent commit overwrites GET_DEGRADED result prior to GET_STATE and it
> is not set again if GET_STATE has not been requested. As GET_STATE
> provides the same information as GET_DEGRADED, the latter is not needed
> anymore. Remove GET_DEGRADED option and replace it with GET_STATE
> option.
>
> Don't count number of failed disks looking at sysfs entries but
> calculate it at the end. Do it only for arrays as containers report
> no disks, just spares.
Hi Tomasz,
I have been sitting on a stack of patches in this area as I wanted to
test them before pushing them out. I finally got a change to run the
testsuite and pushed them, but your patch no longer applied.
Would you mind having a look at the current trunk and see how you want
to address it?
Thanks,
Jes
next prev parent reply other threads:[~2017-05-19 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 12:17 [PATCH] Get failed disk count from array state Tomasz Majchrzak
2017-05-19 19:43 ` Jes Sorensen [this message]
2017-05-31 10:46 ` [PATCH v2] " Tomasz Majchrzak
2017-06-05 15:12 ` 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=bc4470f4-20bf-c45a-9d96-385e4b46e1e3@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=tomasz.majchrzak@intel.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