On 02/04/2011 05:22 AM, Troels Arvin wrote:
Hello,I just created a new 3TB ext4 filesystem on a RHEL 5.6 server, simply using "mke4fs<device>". When I look a the resulting file system options, I see this: Filesystem features: ext_attr resize_inode dir_index filetype sparse_super large_file But when I look at the file system features of the root file system of a RHEL 6 installation, I get the following features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Does mke4fs really create file systems without journals and extents? If so: What's the point of having a special mke4fs command? When I create a new ext4 file system the next time, which of the following features should I include (which seem to be chosen by RHEL6's installer), apart from making sure that a journal is being used: - flex_bg - uninit_bg - dir_nlink What does huge_file and extra_isize give me?
I would be very careful trying to add non-default ext4 options to 5.6. My experiments in that direction on CentOS5.5 led to immediate kernel panics when trying to mount the resulting filesystem. Adding a journal using '-J' and '-j' options seems safe (I've done it several times before with no problems) - the other ext4 options not so much on the 5.x series.
-- Benjamin Franz _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
