Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fstab pass value is set to 0 for all filesystems (including root) #312

Closed
jacobgkau opened this issue Nov 4, 2022 · 6 comments · Fixed by #315
Closed

fstab pass value is set to 0 for all filesystems (including root) #312

jacobgkau opened this issue Nov 4, 2022 · 6 comments · Fixed by #315

Comments

@jacobgkau
Copy link
Member

Distribution (run cat /etc/os-release): Pop!_OS 22.04

Related Application and/or Package Version (run apt policy $PACKAGE NAME): 0.3.2~1663157572~22.04~d343ec3

Issue/Bug Description: In Pop!_OS, the final value for all lines in /etc/fstab is 0. This field controls the filesystem check (fsck) on boot. Ubuntu has the root partition defaulting to 1 (and other partitions can be set to 2 to be checked after the root partition.)

It looks like this is set here: https://github.com/pop-os/distinst/blob/d343ec3444097afb76ebf9339a1cc736cafab1b2/crates/fstab-generate/src/block.rs

Steps to reproduce (if you know): Install Pop!_OS, check /etc/fstab.

Expected behavior: Other distributions default to or recommend that the root partition have this field set to 1 so the root filesystem is checked on boot.

Other Notes: A user in Mattermost asked about this, and I didn't have a good answer. I'm not sure if this default setting was intentional, but if it was, I couldn't find any previous issues, PRs, or chat conversations about it.

The only reason I can think of for skipping the filesystem check would be saving time on boot, but my understanding is that the check doesn't have to do much if there aren't any issues.

@QuentinMoss
Copy link
Contributor

@jacobgkau cool if I take this one? Might require some feedback

@leviport
Copy link
Member

leviport commented Jan 5, 2023

@QuentinMoss totally! PRs are always welcome. Thanks for the interest!

@QuentinMoss
Copy link
Contributor

QuentinMoss commented Jan 15, 2023

@leviport cool, thanks much. I'll start on this tonight. I was having some build issues to test my original changes on OS X, but I've installed ubuntu for this project so hopefully less friction

@QuentinMoss
Copy link
Contributor

@leviport opened a PR here #315

@leviport
Copy link
Member

Thanks for the contribution! The QA team has quite a bit on our plate right now, but we'll get to testing it as soon as we can.

@QuentinMoss
Copy link
Contributor

@leviport fix has been merged.

@jacobgkau jacobgkau linked a pull request Jan 20, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants