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

zfsbootmenu: warn when canmount=on is set for root dataset #424

Merged
merged 1 commit into from
May 13, 2023

Conversation

zdykstra
Copy link
Member

@zdykstra zdykstra commented May 5, 2023

Root datasets should never be automatically mounted. Anything that is considered a root dataset (regardless of a valid kernel/initramfs pair being present) should be checked for canmount=on being set. If it is, throw up a zwarn() . This possibly needs to be more aggressively warned via a timed_prompt - forcing user interaction.

Copy link
Member

@ahesford ahesford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a subtle warning like this or a more obvious, passive indicator is fine. I don't know that we should interrupt regular flow with a timed prompt.

Copy link
Member

@ahesford ahesford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a subtle warning like this or a more obvious, passive indicator is fine. I don't know that we should interrupt regular flow with a timed prompt.

@zdykstra
Copy link
Member Author

zdykstra commented May 6, 2023

Yeah. If we continue to see people impacted by this, the warning can be re-evaluated. For now, a normal warning delivered via the common mechanism is a good start.

@ahesford
Copy link
Member

ahesford commented May 6, 2023

How about this: count the number of root filesystems; if there is exactly one and has canmount=auto, use the unobtrusive logged warning. If there are more than one and any of them have canmount=auto, throw up a timed prompt warning the user that these may fail to boot.

@zdykstra
Copy link
Member Author

zdykstra commented May 6, 2023

I'm checking for the wrong condition - whoops. I'll rework this to count and set a flag file that zfsbootmenu-init can check for.

@zdykstra zdykstra merged commit f688389 into master May 13, 2023
2 checks passed
@zdykstra zdykstra deleted the bafustication-alarm branch June 12, 2023 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants