From: NeilBrown <neilb@suse.de>
To: George Duffield <forumscollective@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Understanding raid array status: Active vs Clean
Date: Mon, 23 Jun 2014 12:01:02 +1000 [thread overview]
Message-ID: <20140623120102.7d85ac52@notabene.brown> (raw)
In-Reply-To: <CAG__1a4kX1gM+ntmcLkevCm6kwVbgSMGmPi-ec6+b1RGKznouw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On Sun, 22 Jun 2014 16:32:31 +0200 George Duffield
<forumscollective@gmail.com> wrote:
> Can anyone give me some hints as to why this array would remain Active
> rather than report Clean? Any help/ insights much appreciated.
It is a mystery.
>
> On Wed, Jun 18, 2014 at 6:04 PM, George Duffield
> <forumscollective@gmail.com> wrote:
> > # cat /sys/block/md0/md/safe_mode_delay returns:
> >
> > 0.203
> >
> > changing the value to 0.500:
> > # echo 0.503 > /sys/block/md0/md/safe_mode_delay
> >
> > makes no difference to the array state.
What if you write a smaller number? e.g. 0.1
What does /sys/block/md0/md/array_state show?
If you "echo clean" into that file, does that "fix" it?
Does it stay fixed if you write to the array?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-06-23 2:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 20:08 Understanding raid array status: Active vs Clean George Duffield
2014-05-28 18:05 ` George Duffield
2014-05-29 5:16 ` NeilBrown
2014-05-29 5:52 ` forumscollective
2014-05-29 6:06 ` NeilBrown
2014-06-17 14:31 ` George Duffield
2014-06-18 13:25 ` George Duffield
2014-06-18 14:31 ` George Duffield
2014-06-18 15:03 ` Robin Hill
2014-06-18 15:57 ` George Duffield
2014-06-18 16:04 ` George Duffield
2014-06-22 14:32 ` George Duffield
2014-06-23 2:01 ` NeilBrown [this message]
2014-06-28 3:01 ` George Duffield
2014-06-28 5:29 ` 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=20140623120102.7d85ac52@notabene.brown \
--to=neilb@suse.de \
--cc=forumscollective@gmail.com \
--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.