From: "Rob Emanuele" <rje@cyan.com>
To: "'Neil Brown'" <neilb@cse.unsw.edu.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Fixing a non-redundant raid
Date: Thu, 20 Feb 2003 10:59:03 -0800 [thread overview]
Message-ID: <000001c2d912$22da8460$a301a8c0@rje1xp> (raw)
In-Reply-To: <15954.51227.385648.487733@notabene.cse.unsw.edu.au>
Thanks! It all worked and the data is consistant.
You guys rock!
--Rob
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Neil Brown
Sent: Tuesday, February 18, 2003 3:56 PM
To: Rob Emanuele
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fixing a non-redundant raid
On Tuesday February 18, rje@cyan.com wrote:
> I've got a raid that I was running w/o a spare disk. One of the
> drives was being flakey and I restarted the machine and I was
> wondering if I can recover the data on the raid. It did not have a
> spare disk. There are 12 drives in the stripe set. According the the
> logs one drive isn't listed as a raid drive (sdi1) and the other's
> (sdb1) event counter is behind. Is there anything I can do or is it a
> loss and I should rebuild the array with a hot spare :)?
>
> I attached the logs.
>
> Thanks for any help,
>
> Rob
Get mdadm, assemble with --force.
e.g.
mdadm --assemble --force /dev/md0 /dev/sd[abcdefghijkl]1
NeilBrown
http://www.kernel.org/pub/linux/utils/raid/mdadm/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in the body of a message to majordomo@vger.kernel.org More majordomo
info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2003-02-20 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 23:04 Rob Emanuele
2003-02-18 23:56 ` Neil Brown
2003-02-20 18:59 ` Rob Emanuele [this message]
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='000001c2d912$22da8460$a301a8c0@rje1xp' \
--to=rje@cyan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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
all inboxes | Powered by JetHome®