Talk:Ext4 Howto

From Ext4
Jump to: navigation, search

How to follow the development of ext4-enabled e2fsprogs more closely via git? Does that make sense:

      $ git clone git://
      $ cd e2fsprogs
      $ git checkout -b pu
      Switched to a new branch "pu" 
      $ git branch 
      * pu
      $ git pull git:// pu

Ckujau 21:18, 14 July 2008 (UTC)

At this point I'd probably tell people to follow e2fsprogs via 'next' or 'master', since it's just much easier. We told people to follow 'pu' because there were critically needed patches for ext4 that weren't quite ready to be locked down in stone. But that's no longer necessary now, so for most users, 'master', or 'next' if they want to play with things a bit earlier than those who want something a little more conservative, is probably be best for all but the most die-hard ext4 developers. --Tytso 21:57, 14 July 2008 (UTC)

about "tune2fs -I 256 /dev/DEV"

You may want to add info about that it can take a long time to convert inodesize (for me it have run for about 7 hours now on a 500 GB partition and has still not finished). You may also want to add info about how dangerous for the filessytem it is, if you can abort it and similar information. Xake 00:37, 29 September 2008 (UTC)

Seven hours is not very long. It's already running for 5 days on my 200 GB partition and has still not finished! --2x4ever 06:55, 24 October 2008 (UTC)
Seven hours seems to be excessively long. How long does it normally take to run fsck on your filesystem? As long as you got a message indicating that the operation could be undone using the "e2undo command", it should be safe to interrupt the tune2fs -I and then running the indicated "e2undo command". i.e., you should have seen something like this:
      # tune2fs  -I 256 /dev/thunk/testext4 
      tune2fs 1.41.1 (01-Sep-2008)
      To undo the tune2fs operations please run the command
          e2undo /var/lib/e2fsprogs/tune2fs-testext4.e2undo /dev/thunk/testext4
It does require that the /var/lib/e2fsprogs directory exists. You can also control the directory where the undo file will be stored by editing /etc/mke2fs.conf; see the man page for /etc/mke2fs.conf for more details. Hope this helps...Tytso 20:05, 29 September 2008 (UTC)

You might want to add a note that a converted filesystem becomes unaccessible by grub once the inode size has been converted to 256. Just got bitten by this. It would be best to leave an ext3 /boot partition --Derkjan 10:05, 6 January 2009 (UTC)

Personal tools