From: Redeeman <redeeman@metanurb.dk>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: time limited error recovery and md raid
Date: Fri, 05 Dec 2008 23:09:02 +0100 [thread overview]
Message-ID: <1228514942.16555.95.camel@localhost> (raw)
In-Reply-To: <alpine.DEB.1.10.0812051637360.17806@p34.internal.lan>
On Fri, 2008-12-05 at 16:42 -0500, Justin Piszcz wrote:
>
> On Fri, 5 Dec 2008, Redeeman wrote:
>
> > On Fri, 2008-12-05 at 16:21 -0500, Justin Piszcz wrote:
> >>
> >> On Fri, 5 Dec 2008, Redeeman wrote:
> >>
> >>> On Fri, 2008-12-05 at 16:12 -0500, Justin Piszcz wrote:
> >>>>
> >>>> On Fri, 5 Dec 2008, Redeeman wrote:
> >>>>
> >>>>> On Fri, 2008-12-05 at 16:01 -0500, Justin Piszcz wrote:
> >>>>>>
> >>>>>> On Fri, 5 Dec 2008, Redeeman wrote:
> >>>>>>
> > Okay, you happen to have any knowledge to pass on about current 1tb
> > disks?
> I am still looking for some good 1TiB drives myself. I know one user who
> has 12 of these, 11 in a RAID-5 array and 1 as a spare on a 12-port 3ware
> PCI-X card:
> SAMSUNG Spinpoint F1 HD103UJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s Hard Drive
I guess those look pretty good.
i personally am running WD RE2 and Seagate ES.2 in raids without issues
at all, raid1, but hmm..
>
> I really would like to find a disk with a working NCQ implementation in
> Linux and 3ware and one that works well. In a single disk configuration,
> the WD 750G that I have used for ~1 year+ now has been fine, the problem
> is finding good, reliable disks when used in a raid configuration, that is
> when everything changes.
>
> > sorry to ask so much, but by "this process", do you mean the drive
> > internally doing it rewriting, avoiding the kickout, or do you mean the
> > raid system discovering the disk as faulty, and kicking it? :)
> The process being check or repair as noted by mikylie who also responded to
> this thread, see his response regarding check vs. repair. There is a
> difference, with check/mdraid see mikylie's note, with RAID VERIFY on a 3ware
> controller it will remap bad sectors to others parts of the array as it comes
> across them both during RAID VERIFY and while the array is running live.
>
> Justin.
>
> --
> 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:[~2008-12-05 22:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 20:57 time limited error recovery and md raid Redeeman
2008-12-05 21:01 ` Justin Piszcz
2008-12-05 21:07 ` Redeeman
2008-12-05 21:12 ` Justin Piszcz
2008-12-05 21:18 ` Redeeman
2008-12-05 21:21 ` Justin Piszcz
2008-12-05 21:31 ` Redeeman
2008-12-05 21:42 ` Justin Piszcz
2008-12-05 22:09 ` Redeeman [this message]
2008-12-05 23:52 ` Justin Piszcz
2008-12-06 2:59 ` Redeeman
2008-12-06 9:23 ` Justin Piszcz
2008-12-06 14:33 ` Redeeman
2008-12-06 9:14 ` David Greaves
2008-12-06 9:59 ` Justin Piszcz
2008-12-06 10:32 ` Michal Soltys
2008-12-06 10:53 ` Justin Piszcz
2008-12-05 23:04 ` Redeeman
2008-12-05 23:52 ` Justin Piszcz
2008-12-06 0:42 ` Roger Heflin
2008-12-08 16:59 ` Redeeman
2008-12-08 17:01 ` Justin Piszcz
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=1228514942.16555.95.camel@localhost \
--to=redeeman@metanurb.dk \
--cc=jpiszcz@lucidpixels.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).