On Tue, Sep 30, 2014 at 03:36:17PM -0600, Andreas Dilger wrote: > > > > 1.5a) Always set the large_file feature with a fresh mkfs, insteadl > > of relying on the accident of the resize inode being > 2G! > > I think that 1.5a is definitely the way to go for new mke2fs, I'm a > bit surprised that we didn't do this for "-t ext4" a long time ago > given that we've enabled lots of other features automatically. Yes, I agree that would be a good thing to do. I'll make the change to mke2fs.conf. > There shouldn't be any problem to do this retroactively in e2fsck > and potentially at mount time for filesystems that already have some > features enabled that are post-large_file (e.g. extents, flex_bg, etc.) > This definitely would not impose any compatibility issues, because any > kernel that supports those features already understands large_file. That sounds like a plan. If we only enable it automatically at mount time (iff we mounted the file system read/write) if any of the ext3 or ext4 specific features are enabled, that should be completely safe. In fact the only reason why we shouldn't turn it on unconditionally is because there are other implementations of ext2 (most notably, GNU Hurd and *BSD) which might not support large_file. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
