group.of.nepali.translators team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1597923

Title:
  curtin is unable to create whole disk fat/vfat formats

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Curtin is unable to create FAT/VFAT filesystems on whole disks. The FAT
     filesystem creation utilities do not, by default, support creating a
     FAT filesystem against an unpartitioned device.

     Curtin has been updated to support passing a force flag to the
     utilities to allow custom storage configurations to use FAT/VFAT
     filesystems against such a device.
     
  [Test Case]

   * Install proposed curtin package and deploy Ubuntu to target system
     specifying a VFAT filesystem on top of a whole block device.

    PASS: Ubuntu installation succeeds

    FAIL: Ubuntu installation fails when attempting to format the block
          device on which the VFAT filesystem would reside.
    

  [Regression Potential]

   * Other OSes which may attempt to mount and read a VFAT filesystem
     created in so-called 'superfloppy' format might not recognize the
     filesystem.

  
  [Original Description]
  The mkfs.fat and mkfs.vfat tools do not by default permit the creation of a filesystem on a disk that has not been partitioned. This is not really a limitation of the filesystems themselves; it is just a safety feature to keep people from accidentally overwriting data.

  Since some curtin users may have a need for whole disk fat/vfat
  filesystems, it makes sense to use the '-I' flag for mkfs.vfat
  commands, which forces the tools to work on whole disks. It appears
  that this flag does not interfere with any of the other options in
  mkfs, and so is essentially a force flag, and can just be added to
  family_flag_mappings in block.mkfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1597923/+subscriptions