From: "Peng tao" <bergwolf@gmail.com>
To: "Diego Calleja" <diegocg@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 documentation
Date: Tue, 23 Dec 2008 11:11:56 +0800 [thread overview]
Message-ID: <6149e97b0812221911l397556dau64b7f5935cf9411f@mail.gmail.com> (raw)
In-Reply-To: <20081222235841.7aaaef93@diego-desktop>
Hi, Diego
Thanks for your efforts.
About migrating from ext3 to ext4, you suggested the following:
tune2fs -O extents,uninit_bg,flex_bg,dir_index /dev/yourfilesystem
Tuning on flex_bg isn't supported yet. tune2fs doesn't really do the
magic you want. It just sets the incompatible feature bit in super
block and nothing else. An e2fsck after that won't modify the ondisk
format either. e2fsck doesn't check log_groups_per_flex right
now(might be a bug if superblock corrupts?).
So even if you turn on flex_bg, fs doesn't benefit from flex_bg feature.
On Tue, Dec 23, 2008 at 6:58 AM, Diego Calleja <diegocg@gmail.com> wrote:
> Due to the astounding lack of good end-user documentation about Ext4, I've
> taken the freedom of writing an article about it for the kernelnewbies
> 2.6.28 changelog: http://kernelnewbies.org/Ext4
>
> If you find any error or you have some suggestion, just tell me and I'll
> fix it.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Cheers,
Bergwolf
................
Margaret Mead - "Always remember that you are absolutely unique. Just
like everyone else."
prev parent reply other threads:[~2008-12-23 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 22:58 Ext4 documentation Diego Calleja
2008-12-22 23:44 ` Andreas Dilger
2008-12-23 9:00 ` Diego Calleja
2008-12-23 3:11 ` Peng tao [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=6149e97b0812221911l397556dau64b7f5935cf9411f@mail.gmail.com \
--to=bergwolf@gmail.com \
--cc=diegocg@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