From: Neil Brown <neilb@suse.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: 2 drives failed, one "active", one with wrong event count
Date: Fri, 29 Jan 2010 21:17:19 +1100 [thread overview]
Message-ID: <20100129211719.04595761@notabene> (raw)
In-Reply-To: <alpine.DEB.1.10.1001290502140.15329@uplift.swm.pp.se>
On Fri, 29 Jan 2010 05:17:10 +0100 (CET)
Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Thu, 28 Jan 2010, Mikael Abrahamsson wrote:
>
> > I have a ubuntu 9.04 system with the default mdadm and kernel (2.6.28).
>
> I thought this might be a driver issue, so I tried upgrading to 9.10 which
> contains kernel 2.6.31 and mdadm 2.6.7.1. It seems the sw was unrelated,
> because now during the night three drives were kicked, so I now have 6
> drives, 3 "State: clean", 3 are "State: active", 1 of the "active" ones
> has a different event count. The array shows similar problems, sometimes
> it will assemble will all 6 drives being (S)pares, sometimes it'll
> assemble with 5 drives and shows as "inactive" in /proc/mdstat.
1/ I think you are hitting and mdadm bug in "--assemble --force" that was
fixed in 2.6.8. (git commit 4e9a6ff778cdc58dc).
2/ Don't poke thing in /sys unless you really know what you are doing (though
I don't think this has causes you any problems).
3/ You really need to fix your problem with SATA timeouts or the array is
never going to work.
4/ please (please please) don't use pastebin. Just include the output inline
in the mail message. It is much easer to get at then.
NeilBrown
>
> After finding
> <http://www.linuxquestions.org/questions/linux-general-1/raid5-with-mdadm-does-not-ron-or-rebuild-505361/>
> I tried this:
>
> root@ub:~# cat /proc/mdstat
> Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
> md0 : inactive sdd[0] sdf[7] sdc[4] sdb[2] sdg[6]
> 9767572240 blocks super 1.2
>
> unused devices: <none>
> root@ub:~# cat /sys/block/md0/md/array_state
> inactive
> root@ub:~# echo "clean" > /sys/block/md0/md/array_state
> -bash: echo: write error: Invalid argument
> root@ub:~# cat /sys/block/md0/md/array_state
> inactive
>
> Still no go. Anyone who can help me what might be going wrong here, I
> mean, that a drive is stuck in "active" can't be a very weird event
> state?
>
next prev parent reply other threads:[~2010-01-29 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 9:05 2 drives failed, one "active", one with wrong event count Mikael Abrahamsson
2010-01-29 4:17 ` Mikael Abrahamsson
2010-01-29 7:06 ` Mikael Abrahamsson
2010-01-29 10:17 ` Neil Brown [this message]
2010-01-29 12:09 ` Mikael Abrahamsson
2010-01-29 12:27 ` Mikael Abrahamsson
2010-01-30 21:20 ` Mikael Abrahamsson
2010-01-31 22:37 ` Neil Brown
2010-02-01 7:13 ` Mikael Abrahamsson
2010-02-04 1:03 ` Neil Brown
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=20100129211719.04595761@notabene \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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.