From: Valerie Henson <val_henson@linux.intel.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Choosing and tuning Linux file systems
Date: Mon, 26 Jun 2006 15:01:42 -0700 [thread overview]
Message-ID: <20060626220141.GF19196@goober> (raw)
In-Reply-To: <20060626091357.GQ5817@schatzie.adilger.int>
(Small accident occurred on Andreas' reply, restoring fsdevel and
quoting in entirety.)
On Mon, Jun 26, 2006 at 03:13:57AM -0600, Andreas Dilger wrote:
> On Jun 25, 2006 15:00 -0700, Valerie Henson wrote:
> > Lots of small files: reiser, ext2/3 with 1k blocks
> > More than ~32,000 files in one directory: XFS or reiser
>
> This is actually "more than 32000 subdirectories in one directory".
Yeah, uh, dur. Thanks!
> Unpatched ext3 is "good" up to 1M files and usable up to 10M regular
> files in a single directory.
Good to know the guidelines here. Thanks!
-VAL
> > Choosing journaling mode in ext3
> > - Default is "ordered", usually the right choice
> > - "journal" is slower but guarantees data is on-disk as well
>
> Also good for NFS server or mail spool running in "sync" mode (sync
> writes are linear into the journal).
>
> > - "writeback" is faster but may result in garbage/security leaks in
> > your file data
>
> ... after a crash
>
> > Tuning reiser
> > - I know nothing!!! Help!
>
> Tail packing saves space for small files, hurts performance somewhat.
>
> > Laptop mode
> > - I know almost nothing about this... some kind of write timeout?
>
> Writes are cached until VM pressure forces them to disk (if disk is
> suspended), or there is a read which causes disk to spin up. So,
> chance of data loss if laptop crashes or "suspends" w/o writing it.
>
>
> Cheers, Andreas
> --
> Andreas Dilger
> Principal Software Engineer
> Cluster File Systems, Inc.
prev parent reply other threads:[~2006-06-26 22:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 22:00 Choosing and tuning Linux file systems Valerie Henson
2006-06-25 22:13 ` Matthew Wilcox
2006-06-25 22:26 ` Arjan van de Ven
2006-06-26 7:22 ` Neil Brown
2006-06-26 9:04 ` Nate Diller
2006-06-27 18:46 ` Valerie Henson
2006-06-26 11:10 ` Erik Mouw
2006-06-26 12:36 ` ext2/3 subdirectory limit [WAS: Choosing and tuning Linux file systems] Tomas Hruby
2006-06-26 12:35 ` Arjan van de Ven
2006-06-26 12:54 ` Theodore Tso
2006-06-26 16:25 ` Andreas Dilger
2006-06-26 17:35 ` Chris Wedgwood
2006-06-26 21:03 ` Tomas Hruby
2006-06-26 21:03 ` Chris Wedgwood
2006-06-26 21:13 ` H. Peter Anvin
2006-06-26 12:59 ` Erik Mouw
2006-06-26 21:09 ` Tomas Hruby
[not found] ` <20060626091357.GQ5817@schatzie.adilger.int>
2006-06-26 22:01 ` Valerie Henson [this message]
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=20060626220141.GF19196@goober \
--to=val_henson@linux.intel.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 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.