All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: mdadm --wait doesn't
Date: Sun, 05 Jul 2009 21:54:11 +0100	[thread overview]
Message-ID: <4A5112F3.8080504@anonymous.org.uk> (raw)
In-Reply-To: <cccedfc60907051035o1753ea61r7098c2ea2c8ded9@mail.gmail.com>

On 05/07/2009 18:35, Jon Nelson wrote:
> I was trying to use mdadm --wait a bit ago to wait for a recovery
> operation, but mdadm --wait didn't actually wait.
> 
> Here is md12 after adding /dev/sdf1 back to it.
> 
> md12 : active raid1 sdf1[3] nbd0[2](W)(F) sde[0]
>       72612988 blocks super 1.1 [3/1] [U__]
>       [>....................]  recovery =  3.0% (2195456/72612988)
> finish=51.4min speed=22805K/sec
>       bitmap: 139/139 pages [556KB], 256KB chunk
> 
> However, mdadm /dev/md12 --wait (and --wait-clean) did not wait for
> the recovery to be complete.
> 
> turnip:~ # mdadm /dev/md12 --wait
> turnip:~ # echo $?
> 0
> turnip:~ # mdadm --version
> mdadm - v3.0 - 2nd June 2009
> 
> I would --fail and --remove /dev/sdf1 and try again (with --add), and
> I did this several times, and I could not get it to wait until the
> recovery was complete.
> 
> Am I doing something wrong? Did I mis-read the documentation?

Did you try `mdadm --wait /dev/md12`? For me that returns 1 on a 
fully-up array (where there's nothing to wait for) while `mdadm 
/dev/md12 --wait` returns 0, so they're obviously handled differently. I 
don't really feel like degrading an array to test further, I'll leave it 
to you :-)

Cheers,

John.

  reply	other threads:[~2009-07-05 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05 17:35 mdadm --wait doesn't Jon Nelson
2009-07-05 20:54 ` John Robinson [this message]
2009-07-05 21:37   ` Jon Nelson
2009-07-05 22:28     ` NeilBrown

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=4A5112F3.8080504@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=jnelson-linux-raid@jamponi.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.