From: Andreas Friedrich Berendsen <afberendsen@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Re: May I suggested an update for ext4.txt file?
Date: Wed, 25 Feb 2009 06:14:21 +1300 [thread overview]
Message-ID: <1235495661.11758.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1235494800.11758.28.camel@localhost.localdomain>
>From http://kernelnewbies.org/Ext4 "3.2. Migrate existing Ext3
filesystems to Ext4", instructions to migrate are different from the
ext4.txt file:
/* ----------------------- */
You need to use the tune2fs and fsck tools in the filesystem, and that
filesystem needs to be unmounted. Run:
* tune2fs -O extents,uninit_bg,dir_index /dev/yourfilesystem
After running this command you MUST run fsck. If you don't do it, Ext4
WILL NOT MOUNT your filesystem.
/* -------------------------- *
-- Berendsen
----Original Message-----
From: Andreas Friedrich Berendsen <afberendsen@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: May I suggested an update for ext4.txt file?
Date: Wed, 25 Feb 2009 06:00:07 +1300
kernel 2.6.28.7
efs2prog: 1.41.4
File Documentation/filesystems/ext4.txt states:
...
Or to configure an existing ext3 filesystem to support extents:
# tune2fs -O extents /dev/hda1
....
To convert from ext2 (a very old filesystem :) ) to ext4, it's necessary
to add more options. I'm not sure which one made the trick.
tune2fs -O
has_journal,dir_index,filetype,extent,flex_bg,sparse_super,large_file,huge_file,uninit_bg,dir_nlink,extra_isize
Also, /etc/filesystems does not contain an entry for
ext4. /etc/efs2prog.conf is ok.
-- Berendsen
--
__________________________________________
Andreas Friedrich Berendsen
SCA OCP MSCA A+ Linux+ Network+ HpMASE
prev parent reply other threads:[~2009-02-24 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 17:00 May I suggested an update for ext4.txt file? Andreas Friedrich Berendsen
2009-02-24 17:14 ` Andreas Friedrich Berendsen [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=1235495661.11758.40.camel@localhost.localdomain \
--to=afberendsen@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