From: Krekna Mektek <krekna@gmail.com>
To: Mike Hardy <mhardy@h3c.com>, linux-raid@vger.kernel.org
Subject: Re: RAID 5 inaccessible - continued
Date: Wed, 15 Feb 2006 10:35:14 +0100 [thread overview]
Message-ID: <8b24c8b10602150135l15b3da13s@mail.gmail.com> (raw)
In-Reply-To: <43F1FFE1.2010107@h3c.com>
I tried this one yesterday, with 2.6.15 that is. The same thing
happened, at the bad block sectors it tried and skipped some but after
a minute or two it stopped again.
Hmmmz.
Krekna
2006/2/14, Mike Hardy <mhardy@h3c.com>:
>
>
> Krekna Mektek wrote:
>
> > The dd actually succeeded, and did finish the job in about one day.
> > The badblocks were found after about the first 7 Gigs.
>
> Is this a 3-disk raid5 array? With two healthy disks and one bad disk?
>
> If so, then what you really want is a new kernel (2.6.15+? 2.6.14+?)
> that has raid5 read-error-handling code in it. Neil just coded that up.
>
> If it's missing a disk and has a disk with bad sectors, then you've
> already lost data, but you could use a combination of smart tests and dd
> to zero out those specific sectors (and only those sectors...) then sync
> a new disk up with the array...
>
> -Mike
>
next prev parent reply other threads:[~2006-02-15 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 15:08 RAID 5 inaccessible - continued Krekna Mektek
2006-02-14 8:35 ` Krekna Mektek
2006-02-14 9:40 ` Neil Brown
2006-02-14 10:35 ` Krekna Mektek
[not found] ` <43F1FFE1.2010107@h3c.com>
2006-02-14 17:18 ` Krekna Mektek
2006-02-14 17:41 ` David Greaves
2006-02-15 9:36 ` Krekna Mektek
[not found] ` <8b24c8b10602151218i43886b75h@mail.gmail.com>
[not found] ` <43F3B119.1000800@dgreaves.com>
2006-02-16 14:32 ` Krekna Mektek
2006-02-16 15:08 ` Krekna Mektek
2006-02-16 16:42 ` Krekna Mektek
2006-02-15 9:35 ` Krekna Mektek [this message]
2006-02-15 9:59 ` Burkhard Carstens
2006-02-15 15:09 ` Krekna Mektek
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=8b24c8b10602150135l15b3da13s@mail.gmail.com \
--to=krekna@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mhardy@h3c.com \
/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.