On Fri, Nov 14, 2008 at 1:26 AM, Phillip Susi <psusi@xxxxxxxxxx> wrote: > I noticed that the default inode size for mkfs in e2fsprogs has been changed > to 256 bytes. I noticed this because I am seeing users complain that they > can no longer access their ext partitions using the windows driver, which > only supports normal 128 byte inodes. I'd like to know why this default was > changed. > > As I understand it, the larger inode size means that ea/acl can be stored > directly in the inode. Are there any other benefits? It seems that using > extended attributes is rather uncommon in the first place, and that when > they are used, many files often share them so it would be better to leave > them in the shared data block rather than duplicate them in every inode. > This leaves me wondering where is the common case that benefits from a > larger default inode? The larger inode is also needed to support new features like nanosecond timestamps, creation time, 64-bit inode versions. If you want to override the 256-byte inode default, you can use "-I 128" while formatting your filesystems with mke2fs. Thanks, Kalpak -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
