From: Ming Zhang <mingz@ele.uri.edu>
To: Peter Grandi <pg_xfs@xfs.for.sabi.co.UK>
Cc: Linux XFS <linux-xfs@oss.sgi.com>
Subject: Re: stable xfs
Date: Wed, 19 Jul 2006 09:11:10 -0400 [thread overview]
Message-ID: <1153314670.2691.14.camel@localhost.localdomain> (raw)
In-Reply-To: <17598.2129.999932.67127@base.ty.sabi.co.UK>
On Wed, 2006-07-19 at 11:24 +0100, Peter Grandi wrote:
> >>> On Tue, 18 Jul 2006 21:20:44 -0400, Ming Zhang <mingz@ele.uri.edu> said:
>
> [ ... ]
>
> mingz> when u say large parallel storage system, you mean
> mingz> independent spindles right? but most people will have all
> mingz> disks configured in one RAID5/6 and thus it is not
> mingz> parallel any more.
>
> As I was saying...
>
> pg> Most of the reports about ''corruption'' are consequences
> pg> of not being aware of what it was designed for, how it
> pg> works and how it should be used...
>
> mingz> [ .. ] example on what is an improper use?
> pg> Well, this mailing list is full of them :-).
>
> pg> But then I have seen people building RAIDs stuffing in a
> pg> couple dozen drives from the same shipping box, [ ... ]
>
> :-)
>
> BTW as to these:
>
> * A 64 bit system.
> * With a large, parallel storage system.
> * The block IO system handles all storage errors.
> * With backups of the contents of the storage system.
>
> I forgot a very essential one:
>
> * With lots of RAM, size proportional to that of the largest filesystem.
>
> [ ... ]
>
what kind of "ram vs fs" size ratio here will be a safe/good/proper one?
any rule of thumb? thanks!
hope not 1:1. :)
Ming
next prev parent reply other threads:[~2006-07-19 13:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 15:30 stable xfs Ming Zhang
2006-07-17 16:20 ` Peter Grandi
2006-07-18 22:36 ` Ming Zhang
2006-07-18 23:14 ` Peter Grandi
2006-07-19 1:20 ` Ming Zhang
2006-07-19 5:56 ` Chris Wedgwood
2006-07-19 10:53 ` Peter Grandi
2006-07-19 14:45 ` Ming Zhang
2006-07-22 17:13 ` Peter Grandi
2006-07-20 6:12 ` Chris Wedgwood
2006-07-22 17:31 ` Peter Grandi
2006-07-19 14:10 ` Ming Zhang
2006-07-19 10:24 ` Peter Grandi
2006-07-19 13:11 ` Ming Zhang [this message]
2006-07-20 6:15 ` Chris Wedgwood
2006-07-20 14:08 ` Ming Zhang
2006-07-20 16:17 ` Chris Wedgwood
2006-07-20 16:38 ` Ming Zhang
2006-07-20 19:04 ` Chris Wedgwood
2006-07-21 0:19 ` Ming Zhang
2006-07-21 3:26 ` Chris Wedgwood
2006-07-21 13:10 ` Ming Zhang
2006-07-21 16:07 ` Chris Wedgwood
2006-07-21 17:00 ` Ming Zhang
2006-07-21 18:07 ` Chris Wedgwood
2006-07-24 1:14 ` Ming Zhang
2006-07-22 18:09 ` Peter Grandi
2006-07-22 17:47 ` Peter Grandi
2006-07-22 15:37 ` Peter Grandi
2006-07-18 23:54 ` Nathan Scott
2006-07-19 1:15 ` Ming Zhang
2006-07-19 7:40 ` Martin Steigerwald
2006-07-19 14:11 ` Ming Zhang
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=1153314670.2691.14.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=linux-xfs@oss.sgi.com \
--cc=pg_xfs@xfs.for.sabi.co.UK \
/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