linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Carl Cook <CACook@quantum-sci.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Is It Hopeless?
Date: Mon, 27 Dec 2010 10:04:00 -0500	[thread overview]
Message-ID: <4D18AAE0.40700@turmel.org> (raw)
In-Reply-To: <201012270510.51520.CACook@quantum-sci.com>

[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]

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.

HTH,

Phil

[-- Attachment #2: raidrepair --]
[-- Type: text/plain, Size: 180 bytes --]

#!/bin/bash
#
# Weekly Cron Job to initiate RAID scan/repair cycles

for x in /sys/block/md*/md/sync_action ; do
	echo repair >$x
done

# Process occurs in background kernel tasks

  reply	other threads:[~2010-12-27 15:04 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 [this message]
2010-12-27 21:34               ` Brad Campbell
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=4D18AAE0.40700@turmel.org \
    --to=philip@turmel.org \
    --cc=CACook@quantum-sci.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).