linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Redeeman <redeeman@metanurb.dk>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, linux-raid@vger.kernel.org
Subject: Re: upgrade advice
Date: Wed, 17 Dec 2008 07:59:20 +0100	[thread overview]
Message-ID: <1229497160.22331.73.camel@localhost> (raw)
In-Reply-To: <cccedfc60812161608y29e6c645n6ff7df5c87292374@mail.gmail.com>

On Tue, 2008-12-16 at 18:08 -0600, Jon Nelson wrote:
> On Tue, Dec 16, 2008 at 5:29 PM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> >
> >
> > On Tue, 16 Dec 2008, Jon Nelson wrote:
> >
> >> What about Hitachi?
> >>
> >> Samsung has been my go-to drive for the better part of a decade, and
> >> Seagate hasn't won any favor with me, so I've been relying on Samsung
> >> and Hitachi with great results - so far.
> 
> > Enterprise or 'desktop' disks Jon?
> 
> Desktop. This is what I've got:
> 
> Hitachi Deskstar T7K500 (HDT725032VLA360)
> SAMSUNG SpinPoint T166 series (HD321KJ)
> Seagate Barracuda 7200.10 family (ST3320620AS)*
> WDC WD3200AAKS-75VYA0
> 
> * the seagate has the infamous 3.AAK firmware.
> 
> I've almost always used Hitachi or Samsung, although I often
> "repurpose" drives from friends and I've had quite a few Maxtor and
> Seagate. The Hitachi does seem to run a bit hotter but it is probably
> my favorite drive of the bunch. The Samsung is nice and quiet,
> vibration-free, like the Hitachi and WD.  The Seagate vibrates and is
> the second after the first died within the first few hours.
> 
> If I were to buy replacement drives, I almost always look at Hitachi
> and Samsung first.

What sort of volume of disks are you using, and what loads? (24/7 with
high load?)

> 


  reply	other threads:[~2008-12-17  6:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 11:10 upgrade advice Max Waterman
2008-12-16 11:44 ` Justin Piszcz
2008-12-16 11:49   ` Redeeman
2008-12-16 13:07     ` Justin Piszcz
2008-12-16 14:15       ` Redeeman
2008-12-16 15:57         ` Jon Nelson
2008-12-16 16:10           ` Ryan Wagoner
2008-12-16 16:27           ` Redeeman
2008-12-16 23:29           ` Justin Piszcz
2008-12-17  0:08             ` Jon Nelson
2008-12-17  6:59               ` Redeeman [this message]
2008-12-17 13:26                 ` Jon Nelson
2008-12-17 14:28                   ` David Lethe
2008-12-17 14:37                     ` Jon Nelson
2008-12-17 15:30                       ` David Lethe
2008-12-18  7:36                         ` Redeeman
2008-12-18 16:37                         ` John Robinson
2008-12-18 16:43                           ` Justin Piszcz
2008-12-18 17:18                             ` John Robinson
2008-12-18 19:14                             ` upgrade advice / Disk drive failure rates - real world David Lethe
2008-12-18 22:51                               ` Max Waterman
2008-12-19  4:28                                 ` David Lethe
2008-12-17 14:46                     ` upgrade advice Redeeman
2008-12-17 15:38                       ` Martin K. Petersen
2009-01-13  3:00                         ` Bill Davidsen
2009-01-13  4:37                           ` Martin K. Petersen
2008-12-16 13:09     ` Max Waterman
2008-12-16 13:04   ` Max Waterman

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=1229497160.22331.73.camel@localhost \
    --to=redeeman@metanurb.dk \
    --cc=jnelson-linux-raid@jamponi.net \
    --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).