This is what happens when I try to answer something in the middle of the night. I forget to respond to things (and I still haven't had my coffee). On 9/11/2018 6:19 AM, Carlos E. R. wrote:
On 11/09/2018 00.07, Anton Aylward wrote:
Why did I use Ext4? Well it is built into the kernel. I can load it without any modules.
Oh? This is from my current config: # CONFIG_EXT2_FS is not set # CONFIG_EXT3_FS is not set CONFIG_EXT4_FS=m CONFIG_EXT4_USE_FOR_EXT2=y CONFIG_EXT4_FS_POSIX_ACL=y # CONFIG_EXT4_FS_SECURITY is not set # CONFIG_EXT4_ENCRYPTION is not set # CONFIG_EXT4_DEBUG is not set What about the above config options indicate it is built into the kernel? CONFIG_XFS_FS=y # CONFIG_XFS_QUOTA is not set CONFIG_XFS_POSIX_ACL=y CONFIG_XFS_RT=y # CONFIG_XFS_ONLINE_SCRUB is not set # CONFIG_XFS_WARN is not set # CONFIG_XFS_DEBUG is not set # CONFIG_VXFS_FS is not set Well, as for my statement about ACL's being built in...um...it was the EXT_attrs that were built in. But acl support was builtin to the earliest designs for XFS.
(re: ext4)... But as far as I'm concerned its a bloody awful FS. That division between inode space and data space.
Sad to say, but that division is in XFS as well (from the mkfs.xfs manpage): This specifies the maximum percentage of space i the filesystem that can be allocated to inodes. The default value is 25% for filesystems under 1TB, 5% for filesystems under 50TB and 1% for filesystems over 50TB.
You could use XFS instead. But then, you might need a separate /boot partition. However, I think that ext4 is easier to repair, more resilient and robust for "/". Just a baseless, gut feeling ;-)
I can't remember ever needing to repair root. /usr - about 2-3 times, but for those that can't run off of '/' and make repairs, that's likely a distinction that doesn't make a difference. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org