All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Jeremy Graham <jeremy@doghouse.agency>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: mdadm stuck at 0% reshape after grow
Date: Wed, 6 Dec 2017 13:34:28 +0000	[thread overview]
Message-ID: <5A27F1E4.8010109@youngman.org.uk> (raw)
In-Reply-To: <CAGx2nv546O5v23Pc2BsWQ=G1xKqiZ66FCqN19MneL9d+YtavTA@mail.gmail.com>

On 06/12/17 07:36, Jeremy Graham wrote:
> However mdadm says otherwise
> 
> $ mdadm --examine-badblocks /dev/sd[bcdefg]1
> Bad-blocks list is empty in /dev/sdb1
> No bad-blocks list configured on /dev/sdc1
> No bad-blocks list configured on /dev/sdd1
> Bad-blocks on /dev/sde1:

You'll notice the list is the same for all drives ... so most of those
blocks probably aren't bad, anyway ...

Somehow, it seems to copy the list from one drive, to all the others ...

Cheers,
Wol

  reply	other threads:[~2017-12-06 13:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05  9:41 mdadm stuck at 0% reshape after grow Jeremy Graham
2017-12-05 10:56 ` Wols Lists
2017-12-05 15:49   ` Nix
2017-12-05 15:55 ` 002
2017-12-06  2:51   ` Phil Turmel
2017-12-06  4:33     ` Jeremy Graham
2017-12-06  7:36       ` Jeremy Graham
2017-12-06 13:34         ` Wols Lists [this message]
2017-12-06 14:02         ` 002
2017-12-06 10:49       ` Andreas Klauer
2017-12-06 14:15         ` Phil Turmel
2017-12-06 16:03           ` Andreas Klauer
2017-12-06 16:21             ` Phil Turmel
2017-12-06 18:24               ` 002
2017-12-07  8:40                 ` Jeremy Graham
2017-12-06 20:19               ` Edward Kuns
2017-12-07 10:26                 ` Wols Lists
2017-12-07 13:58                 ` Andreas Klauer
2017-12-07 17:06                   ` Wols Lists
2017-12-07 17:40                   ` Andreas Klauer
2017-12-07 20:31                     ` Wols Lists
2017-12-07 23:40                     ` Wols Lists
2017-12-08  1:25                       ` 002
2017-12-09  0:20                       ` Edward Kuns
2017-12-14 12:43                         ` Brad Campbell
2017-12-14 17:32                           ` Edward Kuns

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=5A27F1E4.8010109@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=jeremy@doghouse.agency \
    --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.