From: Theodore Ts'o <tytso@mit.edu>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>, Jan Kara <jack@suse.com>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 0/3] Remove ext3 filesystem driver
Date: Wed, 15 Jul 2015 19:23:46 -0400 [thread overview]
Message-ID: <20150715232346.GD18400@thunk.org> (raw)
In-Reply-To: <55A67A57.8010502@gmail.com>
On Wed, Jul 15, 2015 at 11:20:55AM -0400, Austin S Hemmelgarn wrote:
>
> There really isn't much of a clear distinction between ext3 and ext4 (at
> least from an end user standpoint), other than the fact that there are some
> options that only the ext4 driver understands (like extent based
> allocation).
Yeah, the main reason why we did the ext3 -> ext4 fork was that adding
64-bit numbers required major surgery, and we didn't want to break a
lot of production users who were using ext3. But from a file system
format perspective, ext2, ext3, and ext4 are the same logical file
system. There are just multiple different implementations, which all
support slightly different sets of file system features:
* Linux's ext2
* Linux's ext3
* Linux's ext4
* Hurd's ext2
* *BSD's ext2
* Grub's ext2/3/4
The last three implementations are in fact independent ones created
from scratch. :-)
Fortunately we use the same file system support code, e2fsprogs, for
all of them, which is good since it has a very extensive set of
regression test sets for our fsck program, and we've continued adding
to it as we add new file system features.
- Ted
next prev parent reply other threads:[~2015-07-15 23:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 10:26 [PATCH 0/3] Remove ext3 filesystem driver Jan Kara
2015-07-15 10:26 ` [PATCH 1/3] doc: Update doc about journalling layer Jan Kara
2015-07-15 10:26 ` [PATCH 3/3] block: Remove forced page bouncing under IO Jan Kara
2015-07-15 11:02 ` [PATCH 0/3] Remove ext3 filesystem driver Nikolay Borisov
2015-07-15 12:47 ` Jan Kara
2015-07-15 14:18 ` Theodore Ts'o
2015-07-15 15:05 ` Randy Dunlap
2015-07-15 15:09 ` Randy Dunlap
2015-07-15 15:11 ` Eric Sandeen
2015-07-15 15:14 ` Randy Dunlap
2015-07-15 15:20 ` Austin S Hemmelgarn
2015-07-15 23:23 ` Theodore Ts'o [this message]
2015-07-16 8:53 ` Jan Kara
2015-07-15 14:47 ` Jens Axboe
2015-07-15 15:01 ` Joe Perches
2015-07-16 7:27 ` Jan Kara
[not found] ` <1436955987-7305-3-git-send-email-jack@suse.com>
2015-07-15 16:58 ` [PATCH 2/3] fs: " Andrew Morton
2015-07-15 17:35 ` Austin S Hemmelgarn
2015-07-28 21:50 ` Bruce Guenter
2015-07-16 9:41 ` Jan Kara
2015-07-29 12:20 ` [PATCH 0/3] " Konstantin Khlebnikov
2015-07-29 13:49 ` Jan Kara
2015-09-27 7:24 ` Pavel Machek
2015-09-28 17:45 ` Theodore Ts'o
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=20150715232346.GD18400@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=ahferroin7@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sandeen@redhat.com \
/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.