From: Andreas Dilger <adilger@sun.com>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH, RFC] Add new "development flag" to the ext4 filesystem
Date: Wed, 23 Jan 2008 14:50:29 -0700 [thread overview]
Message-ID: <20080123215029.GB18433@webber.adilger.int> (raw)
In-Reply-To: <20080123165307.GA32663@mit.edu>
On Jan 23, 2008 11:53 -0500, Theodore Tso wrote:
> Since I'm still hoping that
> some point in the future, fs/ext4 could subsume fs/ext3 so we don't
> have to worry about bug fixes going into fs/ext2 AND fs/ext3 AND
> fs/ext4, I have my own reasons for wanting that.
If any newbie kernel hacker wants a filesystem project, allowing ext4
to mount ext2 filesystems w/o a journal would be very useful. I
suspect that a simple flag check in the ext4_journal_* wrappers of the
jbd2 functions would be enough in many cases.
One of the reasons to keep ext2 around is that ext3 cannot mount the
filesystem without a journal, and removing that limitation for ext4
would bring us one step closer to removing a ton of duplicate code.
Another reason for ext2 vs. ext3 was overhead from journaling, and
that could also be removed by allowing ext4 to mount ext2 filesystems
w/o a journal.
Maybe a good proposal for a Google Summer-of-Code project.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-01-23 21:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 23:17 [PATCH, RFC] Add new "development flag" to the ext4 filesystem Theodore Tso
2008-01-23 3:55 ` Eric Sandeen
2008-01-23 16:53 ` Theodore Tso
2008-01-23 17:04 ` Eric Sandeen
2008-01-23 17:26 ` Theodore Tso
2008-01-23 21:50 ` Andreas Dilger [this message]
2008-01-25 10:05 ` Jan Kara
2008-01-25 10:50 ` Andreas Dilger
2008-01-28 12:16 ` Jan Kara
2008-01-30 22:26 ` supersud501
2008-01-30 22:48 ` Theodore Tso
2008-01-30 23:03 ` supersud501
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=20080123215029.GB18433@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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