From: berk walker <berk@panix.com>
To: Czigola Gabor <czigola@elte.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: big raid5 trouble
Date: Mon, 02 Jan 2006 06:41:41 -0500 [thread overview]
Message-ID: <43B91175.6040200@panix.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0601020418570.15229@Kamorka>
Czigola Gabor wrote:
> On Sun, 1 Jan 2006, berk walker wrote:
>
>> I don 't think that will help you, per se. Why do you say it is your
>> last chance? If you have n-1 disks OK, then you may be OK. If not, a
>> spare will not help. Can you tell us more?
>> b-
>>
>
> So there is a RAID5 array with 4 disks. I had a long power failure,
> and during the boot sequence, I saw that the 4th disk got marked as
> non fresh. I started the process that should bring the 4th disk back
> in the array, but during this the 3th disk died. The 4th disk is now
> marked as spare.
>
> Meanwhile a found the 4k superblock on the disk (strace mdadm -E), and
> I got - from the source of mdadm - the exact location of the spare
> flag. But I guess, I have to recalc the correct checksum of the new
> superblock.(?)
>
The "spare" disk would be just that, spare, like a spare tire for a car,
pressure is up, ready to go. Each drive contained unique information,
which could be reconstructed from the remaining n-1 drives. You now
have 1 drive "the spare" with no data, and an n-2 array. You will
probably lose data, though the 3rd disk might have had errors in an
unused area. You can FORCE the drives back into an array if things
aren't too trashed. I can not tell what is the safest way to do this,
but someone here may.
b-
next prev parent reply other threads:[~2006-01-02 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 22:10 big raid5 trouble Czigola Gabor
2006-01-01 23:24 ` berk walker
2006-01-02 3:24 ` Czigola Gabor
2006-01-02 11:41 ` berk walker [this message]
2006-01-02 14:46 ` Czigola Gabor
2006-01-04 7:16 ` Mitchell Laks
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=43B91175.6040200@panix.com \
--to=berk@panix.com \
--cc=czigola@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).