void-linux / void-linux/void-docs
chroot.md: In fstab, don't set all fs_passno entries to 1 or 2
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 217
- Forks
- 212
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
The docs in chroot.md tell to setup fstab by copying /proc/mounts and then modifying it.
They advise to:
Change the last zero of the entry for / to 1, and the last zero of every other line to 2. These values configure the behaviour of fsck(8).
This is generally not desired for btrfs and xfs filesystems, see fsck.btrfs(8) and
fsck.xfs(8). In addition, f2fs currently seems to have problems with its fsck, so it should be set to 0 here as well (which is what the void-installer is currently doing if it's a root FS).
I also created a PR for the void-installer regarding this: https://github.com/void-linux/void-mklive/pull/229
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read chroot.md and the referenced fsck.btrfs(8) and fsck.xfs(8) documentation first. Update the fstab guidance so fs_passno values account for filesystem-specific behavior, including the f2fs case described in the issue. Done means the rendered chroot documentation no longer recommends assigning 1 or 2 indiscriminately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100