From: Neil Brown <neilb@suse.de>
To: Richard Michael <rmichael-raid@edgeofthenet.org>
Cc: Roger Heflin <rogerheflin@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Why can't I stop these arrays? PATCH
Date: Tue, 24 Jun 2008 08:42:10 +1000 [thread overview]
Message-ID: <18528.9922.990608.442776@notabene.brown> (raw)
In-Reply-To: message from Richard Michael on Sunday June 22
On Sunday June 22, rmichael-raid@edgeofthenet.org wrote:
>
> Since this has come up on the mailing before, is there any interest in
> this trivial one liner? (Perhaps it needs to go elsewhere in the code
> as well.)
>
> diff -u -r mdadm-2.6.7/Manage.c mdadm-2.6.7-local/Manage.c
> --- mdadm-2.6.7/Manage.c 2008-06-05 22:11:04.000000000 -0400
> +++ mdadm-2.6.7-local/Manage.c 2008-06-22 20:35:25.000000000 -0400
> @@ -115,6 +115,7 @@
> if (quiet==0)
> fprintf(stderr, Name ": fail to stop array %s: %s\n",
> devname, strerror(errno));
> + fprintf(stderr, "Perhaps a running process, mounted filesystem or active volume group?\n");
> return 1;
> }
> if (quiet <= 0)
>
Somewhere way down on my TODO list is
Improve error messages to try and really explain what is
going on.
This is in line with that so I'm happy to take it.
However I would at least like the new message to be conditional on
errno == EBUSY
I don't think any other error are possible, but it is good practice,
provides implicit documentation, and guards against possible future
changes.
NeilBrown
next prev parent reply other threads:[~2008-06-23 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 22:35 Why can't I stop these arrays? Richard Michael
2008-06-22 22:58 ` Roger Heflin
2008-06-23 0:46 ` Why can't I stop these arrays? PATCH Richard Michael
2008-06-23 22:42 ` Neil Brown [this message]
2008-06-22 23:55 ` Why can't I stop these arrays? Mikael Abrahamsson
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=18528.9922.990608.442776@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=rmichael-raid@edgeofthenet.org \
--cc=rogerheflin@gmail.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).