From: "Jakob Østergaard" <jakob@unthought.net>
To: Evan Harris <eharris@puremagic.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: RAID5: mkraid --force /dev/md0 doesn't work properly
Date: Mon, 1 Oct 2001 02:41:30 +0200 [thread overview]
Message-ID: <20011001024130.A24589@unthought.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0109301841220.2459-100000@kinison.puremagic.com>
In-Reply-To: <Pine.LNX.4.33.0109301841220.2459-100000@kinison.puremagic.com>; from eharris@puremagic.com on Sun, Sep 30, 2001 at 07:29:06PM -0500
On Sun, Sep 30, 2001 at 07:29:06PM -0500, Evan Harris wrote:
>
> And yes, I'm using the real --force option. :)
Good (hush now, it's a secret ;)
>
> I have a 6 disk RAID5 scsi array that had one disk go offline through a
> dying power supply, taking the array into degraded mode, and then another
> went offline a couple of hours later from what I think was a loose cable.
>
> The first drive to go offline was /dev/sde1.
> The second to go offline was /dev/sdd1.
>
> Both drives are actually fine after fixing the connection problems and a
> reboot, but since the superblocks are out of sync, it won't init.
Ok.
...
[huge snip]
...
>
> I set the first disk that went offline out with a failed-disk directive, and
> tried to recover with a:
>
> mkraid --force /dev/md0
Good !
(to anyone reading this without having read the docs: don't pull this trick
unless you absolutely positively understand the consequences of screwing up
here)
>
> I'm _positive_ that the /etc/raidtab is correct, but it fails to force the
> update with:
>
> DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
> handling MD device /dev/md0
> analyzing super-block
> raid_disk conflict on /dev/sde1 and /dev/sdi1 (1)
> mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
...
Read on
[snip]
> For info, here is my raidtab:
>
> raiddev /dev/md0
> raid-level 5
> nr-raid-disks 6
> nr-spare-disks 0
> chunk-size 256
> persistent-superblock 1
> device /dev/sdd1
> raid-disk 0
> device /dev/sde1
> raid-disk 1
> device /dev/sdf1
> raid-disk 2
> device /dev/sdg1
> raid-disk 3
> device /dev/sdh1
> raid-disk 4
> device /dev/sdi1
> raid-disk 5
> failed-disk 1
Wrong ! device /dev/sdi1 is railed-disk 5 not failed-disk 1,
that's why mkraid is confused.
What you want is:
device /dev/sdd1
raid-disk 0
device /dev/sde1
raid-disk 1
device /dev/sdf1
raid-disk 2
device /dev/sdg1
raid-disk 3
device /dev/sdh1
raid-disk 4
device /dev/sdi1
failed-disk 5
Good luck,
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
next prev parent reply other threads:[~2001-10-01 0:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 0:29 RAID5: mkraid --force /dev/md0 doesn't work properly Evan Harris
2001-10-01 0:41 ` Jakob Østergaard [this message]
2001-10-01 0:51 ` Evan Harris
2001-10-01 3:56 ` Jakob Østergaard
2001-10-01 6:25 ` Evan Harris
2001-10-01 7:36 ` Peter Svensson
-- strict thread matches above, loose matches on Subject: below --
2001-10-01 12:09 Chris Andrews
2001-10-02 5:09 ` Jakob Østergaard
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=20011001024130.A24589@unthought.net \
--to=jakob@unthought.net \
--cc=eharris@puremagic.com \
--cc=linux-kernel@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.