fstab.5 has incorrect description of fs_passno
Bug #1326978 reported by
YannUbuntu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
util-linux (Ubuntu) |
Triaged
|
Low
|
Unassigned |
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 post a comment you must log in.
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.