All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: forumscollective@gmail.com
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Understanding raid array status: Active vs Clean
Date: Thu, 29 May 2014 16:06:23 +1000	[thread overview]
Message-ID: <20140529160623.5b9e37e5@notabene.brown> (raw)
In-Reply-To: <1C901CF6-75BD-4B54-9F5D-7E2C35633CBC@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

On Thu, 29 May 2014 07:52:02 +0200 forumscollective@gmail.com wrote:

> > I doubt there is a difference between Ubuntu and Arch here.
> > 
> > The array should show "active" in "mdadm --detail" output for 200ms after the
> > last write, and then switch to 'clean'.
> > So if you are writing every 100ms, it will always say "active".
> > 
> > NeilBrown
> 
> For some reason this array has never shown Clean status, only Active.
> 
> It isn't written to other than when NFS mounted for adding new content.
> 
> Any idea what would cause constant writing - I presume from what I see that the initial array sync completed?--

Hmmm...
Do the numbers in /proc/diskstats change?

  watch -d 'grep md0 /proc/diskstats'

What is in /sys/block/md0/md/safe_mode_delay?
What if you change that to a different number (it is in seconds and can be
fractional)?

What  kernel version (uname -a)?

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-05-29  6:06 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 [this message]
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
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=20140529160623.5b9e37e5@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.