linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <ric@emc.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: topics for the file system mini-summit
Date: Fri, 26 May 2006 20:49:58 -0400	[thread overview]
Message-ID: <4477A236.3040208@emc.com> (raw)
In-Reply-To: <20060526164856.GQ5964@schatzie.adilger.int>



Andreas Dilger wrote:

>On May 25, 2006  14:44 -0700, Ric Wheeler wrote:
>  
>
>>With both ext3 and with reiserfs, running a single large file system
>>translates into several practical limitations before we even hit the
>>existing size limitations:
>>
>>   ....
>>
>>I know that other file systems deal with scale better, but the question
>>is really how to move the mass of linux users onto these large and
>>increasingly common storage devices in a way that handles these challenges.
>>    
>>
>
>In a way what you describe is Lustre - it aggregates multiple "smaller"
>filesystems into a single large filesystem from the application POV
>(though in many cases "smaller" filesystems are 2TB).  It runs e2fsck
>in parallel if needed, has smart object allocation (clients do delayed
>allocation, can load balance across storage targets, etc), can run with
>down storage targets.
>
>Cheers, Andreas
>--
>Andreas Dilger
>Principal Software Engineer
>Cluster File Systems, Inc.
>
>
>  
>
The approach that lustre takes here is great -  distributed systems 
typically  take into account subcomponent failures as a fact of life & 
do this better than many single system designs...

The challenge is still there on the "smaller" file systems that make up 
Lustre - you can spend a lot of time waiting for just one fsck to finish ;-)

ric


  reply	other threads:[~2006-05-27  0:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 21:44 topics for the file system mini-summit Ric Wheeler
2006-05-26 16:48 ` Andreas Dilger
2006-05-27  0:49   ` Ric Wheeler [this message]
2006-05-27 14:18     ` Andreas Dilger
2006-05-28  1:44       ` Ric Wheeler
2006-05-29  0:11 ` Matthew Wilcox
2006-05-29  2:07   ` Ric Wheeler
2006-05-29 16:09     ` Andreas Dilger
2006-05-29 19:29       ` Ric Wheeler
2006-05-30  6:14         ` Andreas Dilger
2006-06-07 10:10       ` Stephen C. Tweedie
2006-06-07 14:03         ` Andi Kleen
2006-06-07 18:55         ` Andreas Dilger
2006-06-01  2:19 ` Valerie Henson
2006-06-01  2:42   ` Matthew Wilcox
2006-06-01  3:24     ` Valerie Henson
2006-06-01 12:45       ` Matthew Wilcox
2006-06-01 12:53         ` Arjan van de Ven
2006-06-01 20:06         ` Russell Cattelan
2006-06-02 11:27         ` Nathan Scott
2006-06-01  5:36   ` Andreas Dilger
2006-06-03 13:50   ` Ric Wheeler
2006-06-03 14:13     ` Arjan van de Ven
2006-06-03 15:07       ` Ric Wheeler

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=4477A236.3040208@emc.com \
    --to=ric@emc.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-fsdevel@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).