From: Daniel Pittman <daniel@rimspace.net>
To: linux-raid@vger.kernel.org
Subject: Re: raid5 failed while rebuiling - classical problem
Date: Sun, 04 Jul 2010 22:36:10 +1000 [thread overview]
Message-ID: <87aaq7e85h.fsf@rimspace.net> (raw)
In-Reply-To: 20100704101834.42976337@atak.bl.pg.gda.pl
Janek Kozicki <janek_listy@wp.pl> writes:
> fsck finished, fixed a heft of bad inodes, and now everything seems to be
> fine. So now I'm going to upgrade all that, use latest kernel, then switch
> to raid6.
>
> I tested /dev/hda with badblocks read-write tests, and now it works fine,
> which is kind of disappointing, because it caused to me so much trouble.
If that wrote to the failed block it might cause the bad space to be
reallocated, which is by design what modern disks do.
> Its warranty is going to expire in 3 months, but since it works fine now I
> don't think that I could get it replaced. I guess that it will "really die"
> after its warranty will expire...
Depends entirely on your vendor; I have never had any refusal to replace a
disk after the first bad block, reallocated on write on not. Those errors are
tracked and can be reported by the drive, incidentally, so it has not just
vanished away.
Daniel
--
✣ Daniel Pittman ✉ daniel@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
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
prev parent reply other threads:[~2010-07-04 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 14:31 raid5 failed while rebuiling - classical problem Janek Kozicki
2010-07-02 21:18 ` Janek Kozicki
2010-07-02 21:36 ` Roman Mamedov
2010-07-03 11:47 ` Roman Mamedov
2010-07-03 13:51 ` Janek Kozicki
2010-07-04 8:18 ` Janek Kozicki
2010-07-04 12:36 ` Daniel Pittman [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=87aaq7e85h.fsf@rimspace.net \
--to=daniel@rimspace.net \
--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 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.