How to follow the development of ext4-enabled e2fsprogs more closely via git? Does that make sense:
$ git clone git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git $ cd e2fsprogs $ git checkout -b pu Switched to a new branch "pu" $ git branch master * pu $ git pull git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.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.