From: Roman Mamedov <rm@romanrm.ru>
To: hansbkk@gmail.com
Cc: "D.S. Ljungmark" <spider@skuggor.se>,
doug@easyco.com, linux-raid@vger.kernel.org
Subject: Re: md-raid and block sizes
Date: Tue, 28 Dec 2010 16:45:15 +0500 [thread overview]
Message-ID: <20101228164515.06ffa62f@natsu> (raw)
In-Reply-To: <AANLkTin=-0CN-teD5p4H_nFbuZ944DVuDMku3FaD7uv7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]
On Tue, 28 Dec 2010 18:29:26 +0700
hansbkk@gmail.com wrote:
> This doesn't actually relate to the blocksize issue, but a caveat -
> I've heard that these "green" drives are not suitable for use in a
> RAID.
>
> The specific issue is apparently that these drives spin down very
> frequently, but most RAID implementations keep spinning them back up
> again just as frequently (perhaps unnecessarily?), thus causing undue
> wear and tear on the drives' mechanics and ultimately premature
> failure.
>
> Of course this could be spin from the vendors to get people to spend
> more money on the "enterprise" level drives - I personally am a firm
> believer in saving money by buying consumer-level hardware and using
> the savings to buy extra redundancy.
>
> It just so happens that I've bought a batch of Samsung 2TB drives for
> a RAID6 I'm building, and it turns out they are quite similar to the
> WDEARS, both in their use of "new format" 4K blocks and some of the
> green features. I haven't yet detected any undue drive
> stopping/starting, but then again they are so quite I'm not sure how
> to check. . .
>
> Confirmation or refutation of these thoughts would be most welcome.
This all is just FUD and you shouldn't repeat and spread it further, helping
the vendor's marketing department get people spend money on an "Enterprise"
sticker.
WD*EARS/EADS, or at least most older models in that line-up, do indeed unload
their heads after a short period of time, however that in no way inhibits their
usage in RAID (with this issue there's no difference at all, RAID or no RAID),
and is user-adjustable using the WDIDLE3 utility:
https://encrypted.google.com/search?q=WDIDLE3
Samsung drives do not have any spindown/load/unload problems, but be aware of
this: http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-12-28 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 12:00 md-raid and block sizes D.S. Ljungmark
2010-12-27 19:02 ` Doug Dumitru
2010-12-28 11:45 ` John Robinson
[not found] ` <AANLkTikWxCxVUO+O8MXRXRR7Y8R5xGC1Catv-EiNGcDj@mail.gmail.com>
2010-12-28 8:46 ` D.S. Ljungmark
2010-12-28 11:29 ` hansbkk
2010-12-28 11:45 ` Neil Brown
2010-12-28 11:50 ` Mikael Abrahamsson
2010-12-28 11:51 ` Roman Mamedov
2010-12-28 11:45 ` Roman Mamedov [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=20101228164515.06ffa62f@natsu \
--to=rm@romanrm.ru \
--cc=doug@easyco.com \
--cc=hansbkk@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=spider@skuggor.se \
/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).