From: Curt <lightspd@gmail.com>
To: Phil Turmel <philip@turmel.org>
Cc: Anthony Youngman <antlists@youngman.org.uk>,
NeilBrown <neilb@suse.com>,
linux-raid@vger.kernel.org
Subject: Re: hung grow
Date: Tue, 10 Oct 2017 16:29:46 -0400 [thread overview]
Message-ID: <CADg2FGZpeLc5bOPnVb2O0Z=-KjdCv6BRSO0MUHrMMHaDBLVmCg@mail.gmail.com> (raw)
In-Reply-To: <4033a13e-3ea2-e32a-90a3-a5c86e24ed69@turmel.org>
>
> No, that's not good. And blocking the mount process is a disaster.
>
> Please take notes on all device serials vs. MD device # and consider
> trying everything with rescue distro. I generally use SystemRescueCD,
> but anything with the latest stable kernel and mdadm might help.
>
> Phil
>
Figured. Doesn't seem like it's really doing anything, outside taking
100% cpu. Doing a cat of /proc/pid/io shows all 0's.
Anyway. Should I just run an mdadm --stop on the md127 or doing you
think I'll have to do a reboot?
After it's stopped. I'm guessing just boot with a rescue CD and try to
do an assemble and then mount and hope it doesn't do the same thing?
Cheers,
Curt
next prev parent reply other threads:[~2017-10-10 20:29 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 17:18 hung grow Curt
2017-10-04 17:51 ` Anthony Youngman
2017-10-04 18:16 ` Curt
2017-10-04 18:29 ` Joe Landman
2017-10-04 18:37 ` Curt
2017-10-04 18:44 ` Joe Landman
2017-10-04 19:01 ` Anthony Youngman
2017-10-04 19:09 ` Curt
2017-10-04 19:46 ` Anthony Youngman
2017-10-04 20:01 ` Curt
2017-10-04 21:08 ` Anthony Youngman
2017-10-04 21:53 ` Phil Turmel
[not found] ` <CADg2FGbnMzLBqWthKY5Uo__ANC2kAqH_8B1G23nhW+7hWJ=KeA@mail.gmail.com>
2017-10-06 1:25 ` Curt
2017-10-06 11:16 ` Wols Lists
[not found] ` <CADg2FGYc-sPjwukuhonoUUCr3ze3PQWv8gtZPnUT=E4CvsQftg@mail.gmail.com>
2017-10-06 13:13 ` Phil Turmel
2017-10-06 14:07 ` Curt
2017-10-06 14:27 ` Joe Landman
2017-10-06 14:27 ` Phil Turmel
2017-10-07 3:09 ` Curt
2017-10-07 3:15 ` Curt
2017-10-07 20:45 ` Curt
2017-10-07 21:29 ` Phil Turmel
2017-10-08 22:40 ` Curt
2017-10-09 1:23 ` NeilBrown
2017-10-09 1:40 ` Curt
2017-10-09 4:28 ` NeilBrown
2017-10-09 4:59 ` Curt
2017-10-09 5:47 ` NeilBrown
2017-10-09 12:41 ` Curt
2017-10-10 12:08 ` Curt
2017-10-10 13:06 ` Phil Turmel
2017-10-10 13:37 ` Anthony Youngman
2017-10-10 14:00 ` Phil Turmel
2017-10-10 14:11 ` Curt
2017-10-10 14:14 ` Reindl Harald
2017-10-10 14:15 ` Phil Turmel
2017-10-10 14:23 ` Curt
2017-10-10 18:06 ` Phil Turmel
2017-10-10 19:25 ` Curt
2017-10-10 19:42 ` Phil Turmel
2017-10-10 19:49 ` Curt
2017-10-10 19:51 ` Curt
2017-10-10 20:18 ` Phil Turmel
2017-10-10 20:29 ` Curt [this message]
2017-10-10 20:31 ` Phil Turmel
2017-10-10 20:48 ` Curt
2017-10-10 20:47 ` NeilBrown
2017-10-10 20:58 ` Curt
2017-10-10 21:23 ` Curt
2017-10-10 21:56 ` NeilBrown
2017-10-11 0:26 ` Curt
2017-10-11 4:46 ` NeilBrown
2017-10-11 2:20 ` Curt
2017-10-11 4:49 ` NeilBrown
2017-10-11 15:38 ` Curt
2017-10-12 6:15 ` NeilBrown
2017-10-10 14:12 ` Anthony Youngman
2017-10-04 19:06 ` Anthony Youngman
2017-10-04 18:57 ` Anthony Youngman
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='CADg2FGZpeLc5bOPnVb2O0Z=-KjdCv6BRSO0MUHrMMHaDBLVmCg@mail.gmail.com' \
--to=lightspd@gmail.com \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--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 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).