From: Dark Penguin <darkpenguin@yandex.ru>
To: Wols Lists <antlists@youngman.org.uk>,
Phil Turmel <philip@turmel.org>,
linux-raid@vger.kernel.org
Subject: Re: md failing mechanism
Date: Sat, 23 Jan 2016 03:09:56 +0300 [thread overview]
Message-ID: <56A2C4D4.104@yandex.ru> (raw)
In-Reply-To: <56A2BCA1.6070005@youngman.org.uk>
>> Since that was written, 'A' would now include almost-enterprise drives
>> with RAID ratings like the Western Digital Red family. And the
>> recommended timeout for 'C' has drifted upward to 180.
>
> Almost all posts mention WD Reds. It's NOT a recommendation, but seeing
> as I've tended to buy Seagate (note my Barracudas) I looked for the
> Seagate equivalent. They're called NAS drives, and they cost roughly the
> same ... just pointing this out in case people like Seagate or dislike
> WD ... :-)
I would prefer a Seagate over a WD, but with my experience lately, I
don't want any more Seagates, either... I switched to Hitachi, but they
don't make low-speed drives anymore, and they are expensive... I wonder
of those Seagate NAS drives are actually anywhere near "reliable"?..
--
darkpenguin
next prev parent reply other threads:[~2016-01-23 0:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 17:59 md failing mechanism Dark Penguin
2016-01-22 19:29 ` Phil Turmel
2016-01-22 20:00 ` Wols Lists
2016-01-22 21:44 ` Dark Penguin
2016-01-22 22:18 ` Phil Turmel
2016-01-22 22:50 ` Dark Penguin
2016-01-22 23:23 ` Edward Kuns
2016-01-22 23:34 ` Wols Lists
2016-01-23 0:09 ` Dark Penguin [this message]
2016-01-22 22:37 ` Edward Kuns
2016-01-22 23:07 ` Dark Penguin
2016-01-22 23:39 ` Wols Lists
2016-01-23 0:09 ` Dark Penguin
2016-01-23 0:34 ` Phil Turmel
2016-01-23 10:33 ` Dark Penguin
2016-01-23 15:12 ` Phil Turmel
2016-01-22 23:40 ` James J
2016-01-23 0:44 ` Phil Turmel
2016-01-23 14:09 ` Wols Lists
2016-01-23 19:02 ` James J
2016-01-24 22:13 ` Adam Goryachev
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=56A2C4D4.104@yandex.ru \
--to=darkpenguin@yandex.ru \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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).