From: Theodore Tso <tytso@mit.edu>
To: Shehjar Tikoo <shehjart@cse.unsw.edu.au>
Cc: postrishi <postrishi@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Porting Zfs features to ext2/3
Date: Sun, 27 Jul 2008 19:37:07 -0400 [thread overview]
Message-ID: <20080727233707.GA9378@mit.edu> (raw)
In-Reply-To: <488CFB6E.3020602@cse.unsw.edu.au>
On Mon, Jul 28, 2008 at 08:49:18AM +1000, Shehjar Tikoo wrote:
> Hi Ted
>
> Theodore Tso wrote:
>> The btrfs filesystem effort is an attempt to create a filesystem that
>> will leapfrog the ZFS feature set, but it will probably take longer to
>> reach production ready status than ext4.
>
> Since you mention btrfs here and since I've read this earlier too, do
> you know if btrfs will be the default Linux file system in the future,
> like extX has been?
The nature of Linux is such that these sorts of decisions are not made
by anyone other than each individual system administrator, and by the
distributions who choose which filesystem they which to use as the
"default". There is no such thing as an "official" default
filesystem. For example, the Maemo distribution, which Nokia
distributes for use on the N800/N810 devices, uses jffs2 as its
default filesystem, since those devices use a flash storage device.
DragonLinux, which is designed to be installed on top of DOS/Windows
uses UMSDOS as its default distribution.
What happens in the future, who can say? At some point the ext2/3/4
filesystem, which is based fundamentally on a BSD Fast Filesystem
design base, may get displaced by a filesystem which uses some very
different design as a starting point, when the advantages of starting
with that different design outweighs the advantages of backwards
compatibility and broad base of support which is enjoyed by ext2/3/4.
To give one example from the past, filesystems like JFS were
theoretically better than ext3 at the time, but unfortunately all of
the expertise was concentrated in one company (IBM), and so
distributions were slow to accept it. In the meantime, ext3 was able
to add enough features (htree directories, better SMP scalability) to
eventually meet and then surpass JFS's technical advantages.
XFS has a number of technical advantages over ext3, but the number of
people who understand it are small, and people seem to like the tools
built for ext3 --- and now ext4 has a number of features that were
previously exclusive to XFS. XFS is still the best filesystem for
very large, SGI-class machines, however. But for general purpose
computing, most people are more comfortable with ext3.
Yet the fact that we are retaining backwards compatibility with ext3
does constraint our ability to add radical new features. So
eventually some filesystem will probably overtake ext2/3/4. Will that
btrfs? I don't think anyone can answer that question. I *have* been
helping out the btrfs design team, though, giving them advice such as
making sure that they try to gather contributors from a wide variety
of distributions and other Linux companies. So I hope they do become
successful. In the meantime, though, ext4 is a great extension to the
ext2/3 filesystem family. But in the long run, it may very well be
that btrfs will be more successful than some future attempt to create
an ext5; and that's fine.
Regards,
- Ted
next prev parent reply other threads:[~2008-07-27 23:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 8:49 Porting Zfs features to ext2/3 postrishi
2008-07-27 22:49 ` Theodore Tso
2008-07-27 22:49 ` Shehjar Tikoo
2008-07-27 23:37 ` Theodore Tso [this message]
2008-07-28 3:42 ` Shehjar Tikoo
2008-07-27 22:54 ` Eric Anopolsky
2008-07-27 23:38 ` Theodore Tso
2008-07-28 4:15 ` Eric Anopolsky
2008-07-28 12:40 ` Theodore Tso
2008-07-29 3:58 ` Eric Anopolsky
2008-07-29 16:46 ` Ric Wheeler
2008-07-30 6:00 ` Eric Anopolsky
2008-07-29 21:00 ` Szabolcs Szakacsits
2008-07-29 22:52 ` Szabolcs Szakacsits
2008-07-30 1:29 ` Theodore Tso
2008-08-07 12:09 ` Goswin von Brederlow
2008-07-30 1:34 ` Theodore Tso
2008-07-31 0:50 ` Szabolcs Szakacsits
2008-08-04 20:38 ` Szabolcs Szakacsits
2008-08-07 12:01 ` Goswin von Brederlow
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=20080727233707.GA9378@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=postrishi@gmail.com \
--cc=shehjart@cse.unsw.edu.au \
/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.