From: Neil Brown <neilb@cse.unsw.edu.au>
To: c4c3m@oke.net.id
Cc: linux-raid@vger.kernel.org
Subject: Re: raid 5 on linux --againnnn (sorryy it's big)
Date: Fri, 25 Jul 2003 15:46:36 +1000 [thread overview]
Message-ID: <16160.50236.215350.204806@gargle.gargle.HOWL> (raw)
In-Reply-To: message from c4c3m@oke.net.id on Friday July 25
On Friday July 25, c4c3m@oke.net.id wrote:
> this is the messages from faulty machine:
> #mdadm.static -Eb /dev/sdc*
>
> ARRAY /dev/md4 level=raid5 num-devices=3 UUID=12a3daa6:98bc6aca:98d38bed:
> 414bad01
> devices=/dev/sdc9
> ARRAY /dev/md3 level=raid5 num-devices=3 UUID=5c4fb8f2:7aad3154:83515188:
> 5945a00b
> devices=/dev/sdc8
> ARRAY /dev/md2 level=raid5 num-devices=3 UUID=31788297:ac6dab84:1dc952b3:
> fec35535
> devices=/dev/sdc7
> ARRAY /dev/md1 level=raid5 num-devices=3 UUID=ed01ad73:e4a5e4d0:90eb9b59:
> 15e5c3c0
> devices=/dev/sdc6
> ARRAY /dev/md8 level=raid5 num-devices=3 UUID=1708a6d1:96874201:39d9f451:
> bed35249
> devices=/dev/sdc13
> ARRAY /dev/md7 level=raid5 num-devices=3 UUID=f385575d:d3185f42:37e7d321:
> 4784a76c
> devices=/dev/sdc12
> ARRAY /dev/md6 level=raid5 num-devices=3 UUID=cdcae134:499035b2:e539a33a:
> 636fa315
> devices=/dev/sdc11
> ARRAY /dev/md5 level=raid5 num-devices=3 UUID=59f4a4fc:40471289:9d6e0430:
> 44f950a1
> devices=/dev/sdc10
> ARRAY /dev/md9 level=raid5 num-devices=3 UUID=3b2e48f6:efb0795d:6fa8e6c7:
> 18e6d984
> devices=/dev/sdc1,/dev/sdc3,/dev/sdc4
Thanks.
After you sent me separately the whole set of information (/dev/sd*,
not just /dev/sdc* ... why didn't you send it to the list too like I
keep asking?).
It appears that your machine crashed and when it came back up, sdb and
sdc weren't accessable, so all the arrays got confused by the absense
of sdb and sdc.
You can fix it all up using the "-Af" or "--assemble --force" options
to mdadm.
so
mdadm -Af /dev/md1 /dev/sd[abc]6
mdadm -Af /dev/md3 /dev/sd[abc]8
mdadm -Af /dev/md4 /dev/sd[abc]9
mdadm -Af /dev/md5 /dev/sd[abc]10
mdadm -Af /dev/md6 /dev/sd[abc]11
should make it mostly happy again.
This will make all of the raid5 array out of just two drives, the
'best' two in each case.
Then you can add the third in. e.g.
mdadm /dev/md1 -a /dev/sdc6
Note: this assumes it was sdc6 that was left out. You should
check (mdadm -D /dev/md1 is a good way) and add in the missing
drive.
NeilBrown
next prev parent reply other threads:[~2003-07-25 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 4:53 raid 5 on linux --againnnn (sorryy it's big) c4c3m
2003-07-25 5:46 ` Neil Brown [this message]
2003-07-25 6:11 ` c4c3m
2003-07-25 6:52 ` Neil Brown
[not found] ` <36863.202.158.96.2.1059115951.power.web.id@mail2.oke.net.id>
2003-07-25 6:59 ` 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=16160.50236.215350.204806@gargle.gargle.HOWL \
--to=neilb@cse.unsw.edu.au \
--cc=c4c3m@oke.net.id \
--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