Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Guy Watkins" <linux-raid@watkins-home.com>
To: "'Majed B.'" <majedb@gmail.com>,
	'Chris Green' <cgreen@valvesoftware.com>
Cc: linux-raid@vger.kernel.org
Subject: RE: md software raid
Date: Tue, 27 Oct 2009 23:26:41 -0400	[thread overview]
Message-ID: <90A3FDA136DB4CA4A2C7F34010805951@m5> (raw)
In-Reply-To: <70ed7c3e0910271952o40f3cc3as34cfa88cd5d89279@mail.gmail.com>

} -----Original Message-----
} From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
} owner@vger.kernel.org] On Behalf Of Majed B.
} Sent: Tuesday, October 27, 2009 10:52 PM
} To: Chris Green
} Cc: linux-raid@vger.kernel.org
} Subject: Re: md software raid
} 
} Thanks for the numbers Chris! I guess I kind of anticipated that,
} which is why I suggested using a compressed form, sort of like
} zip/rar...
} 
} Though if the data is mostly multimedia, then I guess it's pointless.
} 
} Punch-cards, anyone?

1 TBytes on punch cards would stack 1,973 miles high.  Assuming 100 cards
per inch and 80 bytes per card.  :)

} 
} On Wed, Oct 28, 2009 at 5:45 AM, Chris Green <cgreen@valvesoftware.com>
} wrote:
} > I'm guessing you could get about a megabyte per sheet of paper this way.
} > So a 1TB drive would take up 1000000 sheets of paper. Looking at
} staples.com,
} > it looks like that would cost you in the neighborhood of $8000. The ink
} cartridges
} > would probably cost more, not to mention the cost of a place to store it
} :-)
} --
}        Majed B.


  reply	other threads:[~2009-10-28  3:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23  9:11 md software raid ian.d
2009-10-23  9:38 ` Robin Hill
2009-10-27 10:19   ` Ian Docherty
2009-10-27 20:52     ` Bill Davidsen
2009-10-27 20:55       ` Richard Scobie
2009-10-27 21:15         ` Christopher Chen
2009-10-28  0:45       ` Leslie Rhorer
2009-10-28  0:47         ` Majed B.
2009-10-28  0:52           ` Leslie Rhorer
2009-10-28  0:58             ` Majed B.
2009-10-28  0:50               ` Richard Scobie
2009-10-27 22:00                 ` Ric Wheeler
2009-10-28 15:08                   ` Eric Sandeen
2009-10-28 16:06                     ` Bernd Schubert
2009-10-28 23:39                       ` Dave Chinner
2009-10-28  1:09                 ` Max Waterman
2009-10-28  1:10                 ` Majed B.
2009-10-28  2:03                   ` Richard Scobie
2009-10-28  2:11                   ` Leslie Rhorer
2009-10-28  2:26                     ` Majed B.
     [not found]                       ` <4D87015385157D4285D56CA6101072FF3A6675B8@exchange07.valvesoftware.com>
2009-10-28  2:52                         ` Majed B.
2009-10-28  3:26                           ` Guy Watkins [this message]
2009-10-28  3:08                         ` Leslie Rhorer
2009-10-28  3:11                           ` Chris Green
2009-10-28  3:29                             ` Leslie Rhorer
2009-11-05 13:51                               ` Matt Garman
2009-10-28  3:35                             ` Guy Watkins
2009-10-28 11:27                               ` Max Waterman
2009-10-28  2:54                       ` Leslie Rhorer
2009-10-28  3:50             ` Christoph Hellwig
2009-10-28  6:37               ` Leslie Rhorer

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=90A3FDA136DB4CA4A2C7F34010805951@m5 \
    --to=linux-raid@watkins-home.com \
    --cc=cgreen@valvesoftware.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=majedb@gmail.com \
    /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