linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Noll <maan@systemlinux.org>
To: Artur Wojcik <artur.wojcik@intel.com>
Cc: linux-raid@vger.kernel.org, dan.j.williams@intel.com,
	ed.ciechanowski@intel.com
Subject: Re: [mdadm PATCH] Kill: fix when zeroing busy devices.
Date: Thu, 28 Jan 2010 17:31:57 +0100	[thread overview]
Message-ID: <20100128163157.GT7517@skl-net.de> (raw)
In-Reply-To: <20100128154844.31790.44309.stgit@awojcik-linux>

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

On 16:48, Artur Wojcik wrote:
> mdadm should not wait indefinitely when it trys to reset
> superblock on device which is busy (cannot be opened).
> 
> Signed-off-by: Artur Wojcik <artur.wojcik@intel.com>
> ---
>  Kill.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Kill.c b/Kill.c
> index 63442a6..a65b865 100644
> --- a/Kill.c
> +++ b/Kill.c
> @@ -46,7 +46,7 @@ int Kill(char *dev, struct supertype *st, int force, int quiet, int noexcl)
>  			fprintf(stderr, Name ": Couldn't open %s for write - not zeroing\n",
>  				dev);
>  		close(fd);
> -		return 1;
> +		return 2;
>  	}
>  	if (st == NULL)
>  		st = guess_super(fd);

Jup.

	Acked-by: Andre Noll <maan@systemlinux.org>

BTW: Mind to kill the close(fd) as well (as fd is negative) while
we're at it? A comment that explains the meaning of the return value
would also be nice.

Thanks
Andre
-- 
The only person who always got his work done by Friday was Robinson Crusoe

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2010-01-28 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 15:48 [mdadm PATCH] Kill: fix when zeroing busy devices Artur Wojcik
2010-01-28 16:31 ` Andre Noll [this message]
2010-01-29 10:02   ` Neil Brown

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=20100128163157.GT7517@skl-net.de \
    --to=maan@systemlinux.org \
    --cc=artur.wojcik@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).