From: Andreas Dilger <adilger@dilger.ca>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Documenting the ext3 -> ext4 transition
Date: Thu, 3 Sep 2015 15:12:00 -0600 [thread overview]
Message-ID: <FDEAB7F2-10F9-451F-ABBE-BBAA37FC4193@dilger.ca> (raw)
In-Reply-To: <20150903191644.GC10390@birch.djwong.org>
On Sep 3, 2015, at 1:16 PM, Darrick J. Wong <darrick.wong@oracle.com> wrote:
>
> Hi all,
>
> Now that ext3.ko is going away, Ted and I talked about having a wiki
> page to talk about the transition (to using ext4.ko for ext3 FS) and
> potential upgrade paths. There already was a section in the HOWTO,
> but I promoted it to its own page and a link from the front page:
>
> Please take a look and suggest/make changes:
>
> https://ext4.wiki.kernel.org/index.php/UpgradeToExt4
I thought is that ext3 had dir_index enabled by default, so it isn't
totally correct that this feature needs to be enabled when upgrading
from ext3 to ext4.
Cheers, Andreas
prev parent reply other threads:[~2015-09-03 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 19:16 Documenting the ext3 -> ext4 transition Darrick J. Wong
2015-09-03 21:12 ` Andreas Dilger [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=FDEAB7F2-10F9-451F-ABBE-BBAA37FC4193@dilger.ca \
--to=adilger@dilger.ca \
--cc=darrick.wong@oracle.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