From: Neil Brown <neilb@suse.de>
To: Iustin Pop <iusty@k1024.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Expose the degraded status of an assembled array through sysfs
Date: Fri, 12 Oct 2007 12:20:44 +1000 [thread overview]
Message-ID: <18190.55804.547483.730045@notabene.brown> (raw)
In-Reply-To: message from Iustin Pop on Wednesday October 10
On Wednesday October 10, iusty@k1024.org wrote:
> On Mon, Sep 10, 2007 at 06:51:14PM +0200, Iustin Pop wrote:
> > The 'degraded' attribute is useful to quickly determine if the array is
> > degraded, instead of parsing 'mdadm -D' output or relying on the other
> > techniques (number of working devices against number of defined devices, etc.).
> > The md code already keeps track of this attribute, so it's useful to export it.
> >
> > Signed-off-by: Iustin Pop <iusty@k1024.org>
> > ---
> > Note: I sent this back in January and it people agreed it was a good
> > idea. However, it has not been picked up. So here I resend it again.
>
> Ping? Neil, could you spare a few moments to look at this? (and sorry for
> bothering you)
Yeh.... thanks for your patience. September was not a good time for
getting my attention.
Yes, I think this is both sensible and useful.
I might just change......
> > @@ -2842,6 +2842,12 @@ sync_max_store(mddev_t *mddev, const char *buf, size_t len)
> > static struct md_sysfs_entry md_sync_max =
> > __ATTR(sync_speed_max, S_IRUGO|S_IWUSR, sync_max_show, sync_max_store);
> >
> > +static ssize_t
> > +degraded_show(mddev_t *mddev, char *page)
> > +{
> > + return sprintf(page, "%i\n", mddev->degraded);
> > +}
... the %i to a %d though. At first I thought it was a typo, but
then checked the man page and discovered that %d and %i both mean the
same thing (so why support them both I wonder).
Thanks,
NeilBrown
prev parent reply other threads:[~2007-10-12 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 16:51 [PATCH] Expose the degraded status of an assembled array through sysfs Iustin Pop
2007-10-10 6:31 ` Iustin Pop
2007-10-12 2:20 ` Neil Brown [this message]
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=18190.55804.547483.730045@notabene.brown \
--to=neilb@suse.de \
--cc=iusty@k1024.org \
--cc=linux-raid@vger.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