Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Christian Schmidt <charlie@digadd.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: What exactly does echo check > /sys/block/mdX/md/sync_action do?
Date: Mon, 10 Jan 2011 11:43:29 +1100	[thread overview]
Message-ID: <20110110114329.091d577c@notabene.brown> (raw)
In-Reply-To: <4D2A5297.6000601@digadd.de>

On Mon, 10 Jan 2011 01:28:07 +0100 Christian Schmidt <charlie@digadd.de>
wrote:


> > This device thinks that that the array is functioning correctly with no
> > failed devices, and that this device is a spare - presumably a 5th device?
> > It doesn't know the names of the other devices (and if it thought it did, it
> > could easily be wrong as names changed).  What do the other devices think of
> > the state of the array?
> 
> [~]>mdadm -Q --detail /dev/md3
> /dev/md3:
>         Version : 1.02
>   Creation Time : Sat Jul 17 02:57:27 2010
>      Raid Level : raid5
>      Array Size : 5857390080 (5586.04 GiB 5997.97 GB)
>   Used Dev Size : 1952463360 (1862.01 GiB 1999.32 GB)
>    Raid Devices : 4
>   Total Devices : 4
>     Persistence : Superblock is persistent
> 
>     Update Time : Mon Jan 10 00:38:00 2011
>           State : clean, recovering
>  Active Devices : 4
> Working Devices : 4
>  Failed Devices : 0
>   Spare Devices : 0
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>  Rebuild Status : 68% complete
> 
>            Name : sysresccd:1
>            UUID : fa8fb033:6312742f:0524501d:5aa24a28
>          Events : 34
> 
>     Number   Major   Minor   RaidDevice State
>        0       8       34        0      active sync   /dev/sdc2
>        1       8       50        1      active sync   /dev/sdd2
>        2       8       82        2      active sync   /dev/sdf2
>        4       8      114        3      active sync   /dev/sdh2
> 
> So just "check" turns the array into rebuild mode and one of the drives
> into a spare? That's unexpected.

I very much doubt writing "check" is all that happened.  Maybe seeing some
kernel logs would help.  
What does
   cat /proc/mdstat

show (assuming the check/recovery/whatever hasn't finished yet).
It should say "recovering" as I think the key word is copied into the
'State:' line above.

But writing "check" should not cause any drive to become a 'spare', and
should not trigger a 'rebuild' - just a 'check'.

NeilBrown


  reply	other threads:[~2011-01-10  0:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09 22:48 What exactly does echo check > /sys/block/mdX/md/sync_action do? Christian Schmidt
2011-01-09 23:26 ` NeilBrown
2011-01-10  0:28   ` Christian Schmidt
2011-01-10  0:43     ` NeilBrown [this message]
2011-01-10  1:14       ` Christian Schmidt

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=20110110114329.091d577c@notabene.brown \
    --to=neilb@suse.de \
    --cc=charlie@digadd.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox