All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ewan Grantham <ewan.grantham@gmail.com>
To: David Greaves <david@dgreaves.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Preparation advice?
Date: Sun, 28 Nov 2004 08:36:33 -0500	[thread overview]
Message-ID: <6d5bedd8041128053635740144@mail.gmail.com> (raw)
In-Reply-To: <41A9B0D3.4070701@dgreaves.com>

On Sun, 28 Nov 2004 11:04:51 +0000, David Greaves <david@dgreaves.com> wrote:
> Ewan's running 2.4.27 and may have an inconsistency with mdadm counting
> the number of raid devices.
...
> /dev/md0:
>         Version : 00.90.00
>   Creation Time : Sat Nov 27 07:32:34 2004
>      Raid Level : raid5
>      Array Size : 735334656 (701.27 GiB 752.98 GB)
>     Device Size : 245111552 (233.76 GiB 250.99 GB)
>    Raid Devices : 4
>   Total Devices : 5
> Preferred Minor : 0
>     Persistence : Superblock is persistent
> 
>     Update Time : Sat Nov 27 14:14:24 2004
>           State : dirty
>  Active Devices : 4
> Working Devices : 4
>  Failed Devices : 1
>   Spare Devices : 0
...
> what does
>  cat /proc/mdstat
> say?

As noted above, I'm getting an "interesting" discrepancy between the 4
devices I specified in my create and the results from mdadm. The
device seems to be working fine after transferring and playing several
files, but I find the "failed devices" bit particularly concerning.
Haven't found any way to get mdadm to tell me which device it thinks
has failed.

As for the command above, I get:
Personalities : [raid5]
read_ahead 1024 sectors
md0 : active raid5 hdd1[3] hdb1[2] sdd1[1] sdc1[0]
      735334656 blocks level 5, 128k chunk, algorithm 2 [4/4] [UUUU]

unused devices: <none>

Which is what I would have expected. Any ideas?

  reply	other threads:[~2004-11-28 13:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27  4:52 Preparation advice? Ewan Grantham
2004-11-27  8:46 ` Gordon Henderson
2004-11-27 16:25   ` Ewan Grantham
     [not found]     ` <41A8C57A.1060803@dgreaves.com>
2004-11-27 20:39       ` Ewan Grantham
     [not found]         ` <41A8EA54.6090708@dgreaves.com>
     [not found]           ` <6d5bedd8041127135230b95202@mail.gmail.com>
     [not found]             ` <41A91263.1010909@dgreaves.com>
     [not found]               ` <6d5bedd804112716277c31207c@mail.gmail.com>
2004-11-28 11:04                 ` David Greaves
2004-11-28 13:36                   ` Ewan Grantham [this message]
2004-11-28 18:00                     ` Guy
2004-11-28 23:33                       ` Ewan Grantham
2004-11-29  4:44                         ` Guy
2004-11-28 11:07     ` Gordon Henderson

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=6d5bedd8041128053635740144@mail.gmail.com \
    --to=ewan.grantham@gmail.com \
    --cc=david@dgreaves.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.