From: Brad Campbell <brad@wasp.net.au>
To: Phil Turmel <philip@turmel.org>
Cc: Carl Cook <CACook@quantum-sci.com>, linux-raid@vger.kernel.org
Subject: Re: Is It Hopeless?
Date: Tue, 28 Dec 2010 05:34:33 +0800 [thread overview]
Message-ID: <4D190669.8040809@wasp.net.au> (raw)
In-Reply-To: <4D18AAE0.40700@turmel.org>
On 27/12/10 23:04, Phil Turmel wrote:
> On 12/27/2010 08:10 AM, Carl Cook wrote:
>>> Every time I read/hear this I cringe. If that is the case your data is worthless to begin with so just delete it all right now. You are literally saying the same thing with your statement.
>>
>> No, I'm saying that the MTBF of disk drives is astronomical, and the likelihood of a fail during backup is miniscule. MTBF of tape is hundreds of times sooner. Not to mention that tape would take forever, and require constant tending. This is why it's not used anymore. My storage is 2TB now, but my library is growing all the time. Backing to off-line disk storage is the only practical way now, given the extremely low cost and high capacity and speed. Each WD 2TB drive is $99 from Newegg! Astounding. Thanks for the input though.
>>
>>
>> On Sun 26 December 2010 21:35:03 Phil Turmel wrote:
>>> I, too, use an alternate server to back up to, but my daily changes are small enough to rsync over the net. To reduce the chance of double failures in my arrays, a cron job kicks off a "resync" weekly.
>>
>> Can you please give some detail on your sync scripts? I've never done this and am not a programmer, but I'm a pretty good shade-tree admin.
>
> Sure. Attached. Note that the script doesn't set the sysctls for speed limits... The defaults are fine for me.
Hrm.. I used to do this too, until a silent corruption issue with a controller trashed 8TB of data.
Now if I'd done a "check" instead of a repair, and been alerted to the fact the controller was
corrupting data rather than blindly overwriting the parity blocks I'd have had a chance of saving
the array.
Checksum and test regularly!.
I do have a backup regime, however I do a full rotation every 3 months and it was approximately 3
months and 5 days before I noticed I really had a problem.
Brad
--
Dolphins are so intelligent that within a few weeks they can
train Americans to stand at the edge of the pool and throw them
fish.
next prev parent reply other threads:[~2010-12-27 21:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 18:19 Is It Hopeless? Carl Cook
2010-12-26 20:11 ` Neil Brown
2010-12-26 20:19 ` Carl Cook
2010-12-26 20:19 ` CoolCold
2010-12-26 20:33 ` Neil Brown
2010-12-26 21:14 ` Berkey B Walker
2010-12-27 0:06 ` Carl Cook
2010-12-27 4:45 ` Stan Hoeppner
2010-12-27 5:35 ` Phil Turmel
2010-12-27 13:10 ` Carl Cook
2010-12-27 15:04 ` Phil Turmel
2010-12-27 21:34 ` Brad Campbell [this message]
2010-12-27 16:37 ` Stan Hoeppner
2010-12-28 1:36 ` Berkey B Walker
2010-12-28 4:16 ` Carl Cook
2010-12-29 3:04 ` Stan Hoeppner
2010-12-29 5:34 ` Roman Mamedov
2011-01-04 20:03 ` Phillip Susi
2011-01-05 21:19 ` Leslie Rhorer
2011-01-05 14:45 ` Hank Barta
2011-01-05 23:07 ` Leslie Rhorer
2011-01-06 23:02 ` Berkey B Walker
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=4D190669.8040809@wasp.net.au \
--to=brad@wasp.net.au \
--cc=CACook@quantum-sci.com \
--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).