From: Andreas Dilger <adilger@clusterfs.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Tomas Hruby <thruby@few.vu.nl>,
Erik Mouw <erik@harddisk-recovery.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: ext2/3 subdirectory limit [WAS: Choosing and tuning Linux file systems]
Date: Mon, 26 Jun 2006 10:25:01 -0600 [thread overview]
Message-ID: <20060626162501.GS5817@schatzie.adilger.int> (raw)
In-Reply-To: <20060626125435.GA3911@thunk.org>
On Jun 26, 2006 08:54 -0400, Theodore Tso wrote:
> We could create an rocompat feature which disabled this, or which
> causes st_nlink above 32000 to mean "infinity"; such patches have
> existed, but in practice it's relatively rare that people actually
> find this to be a limitation, so none of the patches have managed to
> achieve the necessary activation energy to actually get integrated
> into both the kernel and e2fsprogs.
Ted, can you please assign an official RO_COMPAT flag for this feature?
CFS has such patches that we should submit. All that is needed is which
flag should be used.
While you are there, please also assign an RO_COMPAT flag for NS_TIMESTAMP
patch I recently submitted, and INCOMPAT_64BIT for > 32-bit blocknr patches.
There is also EXT3_HUGE_FILE_FL and RO_COMPAT_HUGE_FILE for Takashi's
"i_blocks in fs-blocksize units" patch.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2006-06-26 16:25 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 [this message]
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 ` Choosing and tuning Linux file systems Valerie Henson
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=20060626162501.GS5817@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=erik@harddisk-recovery.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=thruby@few.vu.nl \
--cc=tytso@mit.edu \
/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).