Comment 23 for bug 1365874

Revision history for this message
Simon Iremonger (ubuntu-iremonger) wrote :

OK On further investigation, I have confirmed a lot of key-facts (1 of 2 linked comments).

e2fsprogs 1.44.0-1 backports to xenial with no difficulty whatsoever, passes "make fullcheck" and works in every way I can tell, lots of resizing and checking and use within gparted, etc, all (apparently) behaving...

HOWEVER, for an official xenial-backport (and especially xenial-SRU), to minimize possible problems, I would highly recommend making single change of restoring the 'default' mke2fs.conf EXACTLY (byte-for-byte) as that which came with xenial e2fsprogs 1.42.13-1ubuntu1 :-
https://www.iremonger.me.uk/noidx/e2fs/mke2fs.conf.xenial
This (a) avoids prompting users who've customized their mke2fs.conf about merging-changes, and (b) avoids functional-change for those with automated-deployment-scripts etc. based upon ext4 creation.

I presume, a 'xenial-backport' -or- SRU "proposed" update can be started straight-away? xenial-SRU should DEFINITELY be considered for fsck compatibility with bionic-created FS.