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

Steve Cousins wrote:
>
>
> 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. 

My personal and business system are backed up. On "projects" those who 
write the budget set the policy and I just make sure I have a risk 
assessment with their acceptance in writing. University is not like real 
life in many cases.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  parent reply	other threads:[~2007-02-16 23:09 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
2007-02-16 19:28       ` Justin Piszcz
2007-02-16 23:15         ` Bill Davidsen
2007-02-16 23:09       ` Bill Davidsen [this message]
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=45D639AE.10509@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=steve.cousins@maine.edu \
    /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).