[Bug 1326978] Re: Ubiquity uses fs_passno "1" for the ESP

[Phillip Susi]

The man page is wrong.  Even in the old days this was incorrect; you
just wanted the passno to be different for different filesystems on the
same disk so they would not be checked at the same time and slow each
other down.  Ubuntu uses mountall these days, which treats all non zero
values equally; it uses zero to disable fsck, and otherwise uses a smart
heuristic to fsck one filesystem on each physical disk at a time.


** Package changed: ubiquity (Ubuntu) => util-linux (Ubuntu)

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: util-linux (Ubuntu)
       Status: New => Triaged

** Summary changed:

- Ubiquity uses fs_passno "1" for the ESP
+ fstab.5 has incorrect description of fs_passno

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

Title:
  fstab.5 has incorrect description of fs_passno

Status in “util-linux” package in Ubuntu:
  Triaged

Bug description:
  Ubiquity creates the ESP line in /etc/fstab in a way that conflicts
  with the description of the /etc/fstab in the man page for fstab.

  The 16th paragraph in the man page for fstab describes fs_passno.  It
  is supposed to be 1 for the root filesystem, 2 for all other
  filesystems which are to have fsck run on them, and 0 for all other
  mounts for which fsck is not to be run.

  However, Ubiquity uses fs_passno 1 for the ESP line in fstab.
  Eg, after installing Ubuntu on a UEFI system, the fstab file looks like:
  UUID=4D50-92GF /boot/efi vfat defaults 0 1

  According to the fstab manpage, it should be:
  UUID=4D50-92GF /boot/efi vfat defaults 0 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1326978/+subscriptions