All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Graham <jeremy@doghouse.agency>
To: Phil Turmel <philip@turmel.org>
Cc: 002@tut.by, "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: mdadm stuck at 0% reshape after grow
Date: Wed, 6 Dec 2017 15:33:36 +1100	[thread overview]
Message-ID: <CAGx2nv6YAc5jBL36K0oNG=tE5J3TNXGMvTvD9ZvcZYthXe9Y5g@mail.gmail.com> (raw)
In-Reply-To: <d34ebd38-47e5-35bc-5ee6-0da194ce1901@turmel.org>

Thanks very much for the responses so far all!

@Nix
> That's a kernel bug, probably a deadlock. *Definitely* try a newer
> kernel, 4.14.3 (the latest) if possible. I bet this is fixed by

I tried updating the kernel, bumped to "4.12.5-041205-generic" first
but still no dice.

@002, @Phil
> This feature generally shouldn't be used, because its implementation is
> unfinished. Empty BBL's can be removed from every device by giving
> "--update=no-bbl" option to mdadm on assemble, but before that you
> must manually regenerate content for each block in BBL's and then
> manually zero the lists in superblocks.

I am currently running "badblocks -v /dev/sde1 > sde1.badsectors.txt"
and "badblocks -v /dev/sdf1 > sdf1.badsectors.txt" to see what that
comes back with.

How do I "manually regenerate content for each block in BBL's and then
manually zero the lists in superblocks"? This is uncharted (and
slightly scary) territory for me.

  reply	other threads:[~2017-12-06  4:33 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 [this message]
2017-12-06  7:36       ` Jeremy Graham
2017-12-06 13:34         ` Wols Lists
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='CAGx2nv6YAc5jBL36K0oNG=tE5J3TNXGMvTvD9ZvcZYthXe9Y5g@mail.gmail.com' \
    --to=jeremy@doghouse.agency \
    --cc=002@tut.by \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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.