linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Cousins <steve.cousins@maine.edu>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Changing chunk size
Date: Fri, 16 Feb 2007 13:49:43 -0500	[thread overview]
Message-ID: <45D5FCC7.7000503@maine.edu> (raw)
In-Reply-To: <45D5E05E.4000706@tmr.com>



Bill Davidsen wrote:
> 
> I'm sure "slow" is a relative term, compared to backing up TBs of data 
> and trying to restore them. Not to mention the lack of inexpensive TB 
> size backup media. That's totally unavailable at the moment, I'll live 
> with what I have, thanks.

You don't backup your RAID arrays?  Yikes! For certain data this would 
be fine (data that you can recreate easily) but it sounds like this 
isn't the case for you otherwise you'd just wipe the array and recreate 
the data. There are other modes of failure than just the drives 
themselves (file system corruption for instance) so it is wise to do 
backups, even on "redundant" systems.

Good luck,

Steve
-- 
______________________________________________________________________
  Steve Cousins, Ocean Modeling Group    Email: cousins@umit.maine.edu
  Marine Sciences, 452 Aubert Hall       http://rocky.umeoce.maine.edu
  Univ. of Maine, Orono, ME 04469        Phone: (207) 581-4302



  reply	other threads:[~2007-02-16 18:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 17:16 Changing chunk size Bill Davidsen
2007-02-15 23:24 ` Neil Brown
2007-02-16 16:48   ` Bill Davidsen
2007-02-16 18:49     ` Steve Cousins [this message]
2007-02-16 19:28       ` Justin Piszcz
2007-02-16 23:15         ` Bill Davidsen
2007-02-16 23:09       ` Bill Davidsen
2007-02-18  1:51     ` berk walker
2007-02-18 20:17       ` Bill Davidsen

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=45D5FCC7.7000503@maine.edu \
    --to=steve.cousins@maine.edu \
    --cc=davidsen@tmr.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).