From: James Peverill <jamespev@net1plus.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Resize on dirty array?
Date: Wed, 09 Aug 2006 07:28:53 -0400 [thread overview]
Message-ID: <44D9C6F5.7070501@net1plus.com> (raw)
In-Reply-To: <17625.24594.568139.430440@cse.unsw.edu.au>
I'll try the force assemble but it sounds like I'm screwed. It sounds
like what happened was that two of my drives developed bad sectors in
different places that weren't found until I accessed certain areas (in
the case of the first failure) and did the drive rebuild (for the second
failure). In the future, is there a way to help prevent this? Given
that the bad sectors were likely on different parts of their respective
drives, I should still have a complete copy of all the data right? Is
it possible to recover from a partial two-disk failure using all the disks?
It looks like I might as well cut my losses and buy new disks (I suspect
the last two drives are near death given whats happened to their
brethren). If I go SATA am I better off getting 2 dual port cards or 1
four port?
Thanks again.
James
Neil Brown wrote:
> On Tuesday August 8, jamespev@net1plus.com wrote:
>
>> The resize went fine, but after re-adding the drive back into the array
>> I got another fail event (on another drive) about 23% through the
>> rebuild :(
>>
>> Did I have to "remove" the bad drive before re-adding it with mdadm? I
>> think my array might be toast...
>>
>>
>
> You wouldn't be able to re-add the drive without removing it first.
> But why did you re-add the failed drive? Why not add the new one? Or
> maybe you did...
>
> 2 drives failed - yes - that sounds a bit like toast.
> You can possible do a --force assemble without the new drive and try
> to backup the data somewhere - if you have somewhere large enough.
>
> NeilBrown
>
>
>
>> Any tips on where I should go now?
>>
>> Thanks for the help.
>>
>> James
>>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2006-08-09 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 0:36 Resize on dirty array? James Peverill
2006-08-08 0:46 ` Neil Brown
2006-08-08 19:25 ` James Peverill
2006-08-09 4:09 ` Neil Brown
2006-08-09 11:28 ` James Peverill [this message]
2006-08-09 11:37 ` Martin Schröder
2006-08-09 13:05 ` Mark Hahn
2006-08-09 13:33 ` James Peverill
2006-08-09 21:17 ` David Greaves
2006-08-10 17:44 ` dean gaudet
2006-08-12 1:11 ` David Rees
[not found] ` <72dbd3150608111810m4e4a2e07r5ddcee2132dd6d9a@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0608111813250.29322@twinlark.arctic.org>
2006-08-12 2:05 ` David Rees
2006-08-12 4:36 ` Brad Campbell
2006-08-13 16:02 ` dean gaudet
2006-08-30 7:30 ` dean gaudet
2006-08-11 17:34 ` John Stoffel
2006-08-09 14:56 ` Henrik Holst
2006-08-12 7:22 ` Tuomas Leikola
2006-08-28 4:55 ` Neil Brown
2006-08-28 6:36 ` Mario 'BitKoenig' Holbe
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=44D9C6F5.7070501@net1plus.com \
--to=jamespev@net1plus.com \
--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).