All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: sander@humilis.net
Cc: Gregory Maxwell <gmaxwell@gmail.com>, reiserfs-list@namesys.com
Subject: Re: Fwd: My Dad suggests a redundant copies plugin
Date: Thu, 27 Oct 2005 06:24:03 -0500	[thread overview]
Message-ID: <4360B8D3.30607@slaphack.com> (raw)
In-Reply-To: <20051027071052.GA17692@favonius>

Sander wrote:
> Gregory Maxwell wrote (ao):
> 
>>On 10/25/05, Sander <sander@humilis.net> wrote:


>>Cheaper how? Two disks are cheaper than one?
> 
> 
> If you opt for a copy of everything, yes. Because of a 500GB drive only
> half of it is effectively usable. Two 250GB disks raid1 are much cheaper
> than one 500GB disk.

But not cheaper than one 300 gig disk.  Remember, out of 500 gigs, how
much of that is essential?

If you're doing some sort of media, like video editing, probably a lot,
so you get the two 250 gig disks.  But if you're an author, say, your
life's work probably fits on a single floppy (if you actually use text
files) or at least fifty times over on a CD (if you use some bloaty
office suite).  A programmer?  My entire kernel directory is less than
300 megs, and I haven't run "make clean" recently.

Metadata shouldn't take more than 5% of the disk.

So, if your disk starts going bad and you need to recover, and you lose
a program, so what?  You can still recover the files.  For that matter,
how many people here would be devastated if they lost a .o file?
Probably very few people here have a .o file without a matching .c file,
so if your .o goes, you run "gcc" and you're fine.

Much cheaper, easier than a full backup, easier than RAID, and still
keeps you from losing everything....

Except, you still are your own worst enemy.  I don't think I've ever
lost data to hardware, it was always my own stupidity.

  reply	other threads:[~2005-10-27 11:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25  5:48 My Dad suggests a redundant copies plugin Hans Reiser
2005-10-25  7:25 ` Sander
2005-10-25  9:28   ` Hans Reiser
2005-10-25  9:39     ` Sander
2005-10-25 10:25       ` Konstantin Münning
2005-10-25 19:48         ` David Masover
2005-10-25 10:35     ` Ingo Bormuth
2005-10-26 16:24       ` Gregory Maxwell
2005-10-26 15:49   ` Charles P. Wright
     [not found]   ` <e692861c0510260917r36c2195fp367689753f61b307@mail.gmail.com>
2005-10-26 16:20     ` Fwd: " Gregory Maxwell
2005-10-26 18:22       ` Hans Reiser
2005-10-27  7:10       ` Sander
2005-10-27 11:24         ` David Masover [this message]
     [not found] ` <e692861c0510260911h33c9e2f0x549223c60ddadaef@mail.gmail.com>
2005-10-26 16:19   ` Gregory Maxwell

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=4360B8D3.30607@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=gmaxwell@gmail.com \
    --cc=reiserfs-list@namesys.com \
    --cc=sander@humilis.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.