ext4 metadata_csum and backwards compatibility
Lyn Perrine
walterorlin at gmail.com
Wed Mar 14 21:20:40 UTC 2018
Well I can see option 3 being great if someone boots two different
I think option 3 sounds good as being able to fsck when booting multiple
distros is quite important. Also if a distrohopper using 16.04 as base then
runs vms of multiple other things from their 16.04 base system they can
fsck all their vms on the desktop. I see this as helpful for anyone testing
from 16.04 as a base or having 16.04 installed beside the envelopment
release for testing when eating your own dogfood.
On Wed, Mar 14, 2018 at 6:38 AM, Simon Deziel <simon.deziel at gmail.com>
wrote:
> On 2018-03-14 07:17 AM, Robie Basak wrote:
> > 3) We backport metadata_csum support to Xenial in an SRU[1] without
> > changing the default there. Xenial users will be able to fsck
> > Bionic-created ext4 filesystems. There will be forward compatibilty
> > problems when skipping across multiple LTSs (eg. Trusty accessing a
> > Bionic-created ext4 filesystem), but not across any single LTS.
>
> I'd vote for this ^, SRU to Xenial. When a new LTS arrives, I typically
> test it extensively in VMs running off of an hypervisor running the
> previous LTS. Being able to fsck the VM's filesystem is sometimes
> convenient. Also, since the metadata checksum was enabled in 16.10+ I'd
> rather not go back in terms of default enabled features, especially if
> this one is now production ready.
>
> Regards,
> Simon
>
>
> --
> ubuntu-server mailing list
> ubuntu-server at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-server/attachments/20180314/d74ab523/attachment.html>
More information about the ubuntu-server
mailing list