From: NeilBrown <neilb@suse.de>
To: "Michał Sawicz" <michal@sawicz.net>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Failed, but "md: cannot remove active disk..."
Date: Tue, 15 May 2012 13:38:56 +1000 [thread overview]
Message-ID: <20120515133856.6e04d77b@notabene.brown> (raw)
In-Reply-To: <1336995865.6722.22.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On Mon, 14 May 2012 13:44:25 +0200 Michał Sawicz <michal@sawicz.net> wrote:
> Dnia 2012-05-14, pon o godzinie 21:36 +1000, NeilBrown pisze:
> > Is the array still functioning?
> > Are there any interesting messages appearing in the kernel logs?
>
> Yes and no, the array is fine, working, nothing interesting in any logs
> I can see.
>
> > What does
> > grep . /sys/block/md126/md/dev*/*
> > show?
>
//snip//
Thanks. No hints there - all normal.
If you can write to the array, then md_check_recovery must be getting run,
and the array is not read-only. So...
Is there a 'sync' thread still running? It would be called
md126_resync
That would stop things from progressing.
If there is, what does
cat /proc/$PID/stack
show for the relevant PID ??
What about
cat /sys/block/md126/md/sync_action
??
If that were 'frozen', that might explain it.
cat /sys/block/md126/md/reshape_position
shows "none" I suspect?
I cannot think of anything else that could be getting in the way.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-15 3:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 18:21 Failed, but "md: cannot remove active disk..." Michał Sawicz
2012-05-14 10:22 ` NeilBrown
2012-05-14 10:53 ` Michał Sawicz
2012-05-14 11:36 ` NeilBrown
2012-05-14 11:44 ` Michał Sawicz
2012-05-15 3:38 ` NeilBrown [this message]
2012-05-15 7:56 ` Michał Sawicz
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=20120515133856.6e04d77b@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=michal@sawicz.net \
/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).