From: Christoph Hellwig <hch@lst.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 3/3] ocfs2: Switch over to JBD2.
Date: Fri, 5 Sep 2008 02:32:02 +0200 [thread overview]
Message-ID: <20080905003202.GC29097@lst.de> (raw)
In-Reply-To: <1220497421-8606-4-git-send-email-joel.becker@oracle.com>
On Wed, Sep 03, 2008 at 08:03:41PM -0700, Joel Becker wrote:
> ocfs2 wants JBD2 for many reasons, not the least of which is that JBD is
> limiting our maximum filesystem size.
>
> It's a pretty trivial change. Most functions are just renamed. The
> only functional change is moving to Jan's inode-based ordered data mode.
> It's better, too.
>
> Because JBD2 reads and writes JBD journals, this is compatible with any
> existing filesystem. It can even interact with JBD-based ocfs2 as long
> as the journal is formated for JBD.
>
> We provide a compatibility option so that paranoid people can still use
> JBD for the time being. This will go away shortly.
Having to parallel codepathes switched by a little option is a really
bad idea. Those paranoid people (if they exist at all) should just
stick to an old kernel.
next prev parent reply other threads:[~2008-09-05 0:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 3:03 [Ocfs2-devel] [PATCH 0/3] ocfs2: Switch over to JBD2 Joel Becker
2008-09-04 3:03 ` [Ocfs2-devel] [PATCH 1/3] ocfs2: Limit inode allocation to 32bits Joel Becker
2008-09-05 0:27 ` Christoph Hellwig
2008-09-05 1:38 ` Joel Becker
2008-09-04 3:03 ` [Ocfs2-devel] [PATCH 2/3] ocfs2: Add the 'inode64' mount option Joel Becker
2008-09-05 0:29 ` Christoph Hellwig
2008-09-04 3:03 ` [PATCH 3/3] ocfs2: Switch over to JBD2 Joel Becker
2008-09-04 3:03 ` [Ocfs2-devel] " Joel Becker
2008-09-05 0:32 ` Christoph Hellwig [this message]
2008-09-05 1:40 ` Joel Becker
2008-09-05 10:05 ` [Ocfs2-devel] [PATCH 0/3] " Mark Fasheh
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=20080905003202.GC29097@lst.de \
--to=hch@lst.de \
--cc=ocfs2-devel@oss.oracle.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.