From: "Ákos Maróy" <darkeye@tyrell.hu>
To: Francois Barre <francois.barre@gmail.com>
Cc: Neil Brown <neilb@suse.de>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: raid issues after power failure
Date: Mon, 03 Jul 2006 10:54:32 +0200 [thread overview]
Message-ID: <44A8DB48.8080905@tyrell.hu> (raw)
In-Reply-To: <fd8d0180607020114m5e02e1ek553e5da2941eb6dd@mail.gmail.com>
Francois Barre wrote:
> Well, Neil, I'm wondering,
> It seemed to me that Akos' description of the problem was that
> re-adding the drive (with mdadm not complaining about anything) would
> trigger a resync that would not even start.
> But as your '--force' does the trick, it implies that the resync was
> not really triggered after all without it... Or did I miss a bit of
> log Akos provided that did say so ?
> Could there be a place here for an error message ?
well, thing is it's still not totally OK. after doing an
# mdadm -A --force /dev/md0
# mdadm /dev/md0 -a /dev/sdb1
it starts to re-assemble the array. it takes a lot of time (like about 4
hours), which is OK. after the re-assembly is ready, all seems fine:
# cat /proc/mdstat
Personalities : [raid5] [raid4]
md0 : active raid5 sdb1[1] sda1[0] sdd1[3] sdc1[2]
1172126208 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
unused devices: <none>
# mdadm --query /dev/md0
/dev/md0: 1117.83GiB raid5 4 devices, 0 spares. Use mdadm --detail for
more detail.
# mdadm --query --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Tue Apr 25 16:17:14 2006
Raid Level : raid5
Array Size : 1172126208 (1117.83 GiB 1200.26 GB)
Device Size : 390708736 (372.61 GiB 400.09 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Jul 3 00:16:39 2006
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : 8a66d568:0be5b0a0:93b729eb:6f23c014
Events : 0.2701837
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
#
right? checking with
# mdadm -E /dev/sb[a-d]1
will also show that all drives have the same event count, etc.
but, just doing a
# mdadm --stop /dev/md0
# mdadm -A /dev/md0
will result in the array started with 3 drives out of 4 again. what am I
doing wrong?
Akos
next prev parent reply other threads:[~2006-07-03 8:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 9:12 raid issues after power failure Ákos Maróy
2006-06-30 9:21 ` Francois Barre
2006-06-30 9:25 ` Ákos Maróy
[not found] ` <fd8d0180606300250q6fbab5d3wdf343b530f3119a9@mail.gmail.com>
2006-06-30 9:51 ` Francois Barre
2006-06-30 9:56 ` Francois Barre
2006-06-30 12:29 ` Akos Maroy
2006-06-30 12:40 ` Francois Barre
2006-06-30 12:43 ` Akos Maroy
2006-06-30 12:57 ` Francois Barre
2006-06-30 23:06 ` Neil Brown
2006-07-01 15:28 ` Ákos Maróy
2006-07-02 8:14 ` Francois Barre
2006-07-02 9:26 ` David Greaves
2006-07-03 8:54 ` Ákos Maróy [this message]
2006-07-03 9:16 ` Francois Barre
2006-07-03 11:30 ` Ákos Maróy
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=44A8DB48.8080905@tyrell.hu \
--to=darkeye@tyrell.hu \
--cc=francois.barre@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.