From: Stan Hoeppner <stan@hardwarefreak.com>
To: Erik Gulliksson <erik@gulliksson.org>
Cc: xfs@oss.sgi.com
Subject: Re: XFS corruption on 3ware RAID6-volume
Date: Wed, 23 Feb 2011 10:56:49 -0600 [thread overview]
Message-ID: <4D653C51.3080209@hardwarefreak.com> (raw)
In-Reply-To: <AANLkTinWByYooMnPL7BryPowDexBeiHJdh3aVh+fdm-a@mail.gmail.com>
Erik Gulliksson put forth on 2/23/2011 7:27 AM:
> Dear XFS people,
>
> I have bumped in to a corruption problem with one a XFS filesystems.
> The filesystem lives on a RAID6-volume on a 3ware 9650SE-24M8 with
> battery backup and writecache enabled. RAID6-configuration is 11 2.0TB
> WD15EARS disks and the volume is reported as OK by the RAID-card.
There is a reason WD has an enterprise line of drives for use in RAID
applications. The EARS series, along with the entire WD desktop drive
series, are not suitable for use with hardware RAID controllers, mainly
because they don't support TLER. The 2TB low RPM WD Green at Newegg is
$90. The 2TB 7.2k RPM Enterprise RE4 is $270, exactly 3 times the
price. Is your data, and reliable fast access to it, worth the extra
$1,980?
I think too many folks are blinded by low acquisition cost and thus
can't see the overall life cycle cost, or TCO, of their storage
infrastructure.
Please Google the XFS list archives for the horror story at UC Santa
Cruz WRT hardware arrays using the WD 2TB Green drives. The sysop lost
12TB of a 60TB XFS filesystem, and damn near lost the entire 60TB, if
not for luck. The lost 12TB of data was Ph. D. students' research data.
That kind of data is definitely worth the extra $$ for the right type
of drives which would have avoided the problem.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-02-23 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 13:27 XFS corruption on 3ware RAID6-volume Erik Gulliksson
2011-02-23 14:46 ` Emmanuel Florac
2011-02-23 15:01 ` Erik Gulliksson
2011-02-23 15:23 ` Emmanuel Florac
2011-02-24 10:20 ` Erik Gulliksson
2011-02-23 15:29 ` Justin Piszcz
2011-02-23 15:37 ` Emmanuel Florac
2011-02-23 15:42 ` Justin Piszcz
2011-02-24 10:25 ` Erik Gulliksson
2011-02-24 10:35 ` Erik Gulliksson
2011-02-24 11:01 ` Justin Piszcz
2011-02-24 12:14 ` Emmanuel Florac
2011-02-23 16:56 ` Stan Hoeppner [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=4D653C51.3080209@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=erik@gulliksson.org \
--cc=xfs@oss.sgi.com \
/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