[Bug 1297012] Re: hyper-v: Manual partitioning formats /boot with ext2 file-system

[Abhishek Gupta]

Hi Dimitri,

Thanks for the explanation. The reason we are having trouble with ext2
is because ext2 does not seem to have a freeze file-system interface.
The freeze interface typically flushes all dirty buffers to disk and
allows the creation of a file-system consistent snapshot prior to
backup. If we take a non file-system consistent backup then restoring
the volume later would cause fsck checks that may alarm users or corrupt
the file-system in unknown ways.

We can recommend customers to use ext4 in our documentation however it
is often that people just go with the default choice. This is the reason
why we were wondering if you could change the boot file-system to ext4.

If you do not expect /boot to be modified then wouldn't the journal have
a very low impact anyway? Could we tune the journal to be of a small
size?

Let me know your thoughts.
Thanks,
Abhishek

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to partman-auto in Ubuntu.
https://bugs.launchpad.net/bugs/1297012

Title:
  hyper-v: Manual partitioning formats /boot with ext2 file-system

Status in “partman-auto” package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  It appears that if users manually partition the disk, the /boot
  partition is formatted using the ext2 file-system. This breaks certain
  backup scenarios for Hyper-V. Is it possible to change the default
  format for the /boot partition to ext4?

  Please let us know and see attached image for more details.
  Thanks,
  Abhishek

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1297012/+subscriptions