From: Theodore Ts'o <tytso@mit.edu>
To: Felipe Monteiro de Carvalho <felipemonteiro.carvalho@gmail.com>
Cc: Autif Khan <autif.mlist@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: How to differentiate ext4 from ext2/3 in code?
Date: Wed, 12 Jun 2013 08:52:25 -0400 [thread overview]
Message-ID: <20130612125225.GA26388@thunk.org> (raw)
In-Reply-To: <CACyNnZOXuPWvCDtPuAnGD72g41LWLTyuou_gCKRPHm+ZWemyXA@mail.gmail.com>
On Wed, Jun 12, 2013 at 07:00:57AM +0200, Felipe Monteiro de Carvalho wrote:
> Hello,
>
> Thanks a lot, it was a really good answer =) Just to complement I see that
> some software out there uses EXT4_FEATURE_INCOMPAT_EXTENTS in the incompat
> list. It seams that this flag is usually (always?) set in ext4 but never
> (?) present in ext3
>
> example:
> http://lists.alioth.debian.org/pipermail/parted-devel/2009-January/002488.html
It is true that the extents feature is supported by the ext4 file
system driver, and there exists no versions of the file system drivers
in the Linux kernel which supports the extents feature.
You can certainly construct file systems which have, say, the flex_bg
feature enabled has the same characteristics as the extents feature in
terms of support coverage by ext3 and ext4 implementations in the
Linux kernel, however.
It looks from the patch you've cited that parted is using some
hueristics for the purposes of displaying "ext2" vs "ext3" vs "ext4"
to the user. That's fine from the perspective of simplifying the user
interface, but it can end up confusing the user for some unusual file
system configurations.
Regards,
- Ted
prev parent reply other threads:[~2013-06-12 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 7:04 How to differentiate ext4 from ext2/3 in code? Felipe Monteiro de Carvalho
2013-05-31 15:28 ` Theodore Ts'o
2013-06-03 17:16 ` Autif Khan
[not found] ` <CACyNnZOXuPWvCDtPuAnGD72g41LWLTyuou_gCKRPHm+ZWemyXA@mail.gmail.com>
2013-06-12 12:52 ` Theodore Ts'o [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=20130612125225.GA26388@thunk.org \
--to=tytso@mit.edu \
--cc=autif.mlist@gmail.com \
--cc=felipemonteiro.carvalho@gmail.com \
--cc=linux-ext4@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).