Canonical please read Theodore Tso's Comment #4 above, and consider for Ubuntu 18.04 LTS!
This "64bit,metadata_csum" creates compatibility-issues even with 16.04 LTS, and does not seem to provide a huge benefit [>16TB fs support, slightly stronger metadata checksumming].
This creates all sorts of problems for compatibility/portability of filesystems, e.g.:-
* dual-booting 18.04, even previous LTS version cannot fsck the filesystem.
* "ext4 portable disks" created by 18.04 similarly same problem.
* Also consider how wide is the 64bit,metadata_csum support anyway, users may want disks to work with many distros/drivers? Canonical's commercial-supporters may have views herein?. -- the linked bugreport also mentions another issue with hwe-edge and LVM.
Also note, turning off the 64bit,metadata_csum when required is a total PAIN, needing filesystem offline, fsck and tune2fs in careful concert.....
In my view, the 16.04 LTS mke2fs.conf [ ext4{} stanza with
"auto_64-bit_support = 1" and NO "64bit,metadata_csum" in "features" ]
should be seriously-considered for 18.04 "LTS" (even if 18.10 onwards follow Debian).
As tytso says, this 'change' has been "Decision-by-Default" due to importing a Debian upstream package, I would like Canonical to make an 'informed and considered decision' about this please!.
Canonical please read Theodore Tso's Comment #4 above, and consider for Ubuntu 18.04 LTS!
This "64bit, metadata_ csum" creates compatibility- issues even with 16.04 LTS, and does not seem to provide a huge benefit [>16TB fs support, slightly stronger metadata checksumming].
This creates all sorts of problems for compatibility/ portability of filesystems, e.g.:- supporters may have views herein?. -- the linked bugreport also mentions another issue with hwe-edge and LVM.
* dual-booting 18.04, even previous LTS version cannot fsck the filesystem.
* "ext4 portable disks" created by 18.04 similarly same problem.
* Also consider how wide is the 64bit,metadata_csum support anyway, users may want disks to work with many distros/drivers? Canonical's commercial-
Also note, turning off the 64bit,metadata_csum when required is a total PAIN, needing filesystem offline, fsck and tune2fs in careful concert.....
In my view, the 16.04 LTS mke2fs.conf [ ext4{} stanza with bit_support = 1" and NO "64bit, metadata_ csum" in "features" ] considered for 18.04 "LTS" (even if 18.10 onwards follow Debian).
"auto_64-
should be seriously-
As tytso says, this 'change' has been "Decision- by-Default" due to importing a Debian upstream package, I would like Canonical to make an 'informed and considered decision' about this please!.
Hope that helps!