All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Makuch <linuxraid@makuch.org>
To: linux-raid@vger.kernel.org
Subject: Re: /proc/mdstat docs (was Re: Few questions)
Date: Sat, 08 Dec 2007 22:11:24 -0600	[thread overview]
Message-ID: <475B6AEC.80203@makuch.org> (raw)
In-Reply-To: <475AD13C.3060203@dgreaves.com>

David Greaves wrote:
> Michael Makuch wrote:
>   
>> So my questions are:
>>     
> ...
>   
>> - Is this a.o.k for a raid5 array?
>>     
>
> So I realised that /proc/mdstat isn't documented too well anywhere...
>
> http://linux-raid.osdl.org/index.php/Mdstat
>
> Comments welcome...
>
> David
>   

One thing, in the section "md device line" you describe how to identify 
spare devices,
but you didn't mention the "(S)" which appears after a spare device, at 
least it does on mine:

# uname -a
Linux pecan.makuch.org 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 
2007 i686 i686 i386 GNU/Linux

# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 etherd/e0.0[0] etherd/e0.2[9](S) etherd/e0.9[8] 
etherd/e0.8[7] etherd/e0.7[6] etherd/e0.6[5] etherd/e0.5[4] 
etherd/e0.4[3] etherd/e0.3[2] etherd/e0.1[1]
      3907091968 blocks level 5, 64k chunk, algorithm 2 [9/9] [UUUUUUUUU]
      [==================>..]  resync = 91.0% (444527040/488386496) 
finish=560.9min speed=1301K/sec
unused devices: <none>


Unless that means something else??? But e0.2 is my spare so I'm just 
assuming "(S)" means spare!

Thanks
Mike



      parent reply	other threads:[~2007-12-09  4:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08  0:11 Few questions Michael Makuch
2007-12-08  3:17 ` Guy Watkins
2007-12-08 12:03   ` David Greaves
2007-12-09  4:17   ` Michael Makuch
2007-12-08  3:22 ` Corey Hickey
2007-12-08 17:15 ` /proc/mdstat docs (was Re: Few questions) David Greaves
2007-12-08 19:27   ` Raz
2007-12-09  4:11   ` Michael Makuch [this message]

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=475B6AEC.80203@makuch.org \
    --to=linuxraid@makuch.org \
    --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.