-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add volatile keyword to mount #17
Conversation
LGTM |
Yup I noticed this "volatile" was your kernel contribution @giuseppe . We should probably have volatile on for other throwaway filesystems like:
and
also. There would be some performance savings there too (it should be added in a way that supports kernels without "volatile" support also I guess if it was to be added for Btw, I'm kind of assuming "volatile" made the RHEL 9 kernel in this PR @giuseppe @rhatdan ... Is that true? I tested this on Fedora. |
volatile should be in RHEL 9. Would it make sense to retry the mount command without |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Added reattempt without "volatile" on EINVAL |
initoverlayfs is designed to be throwaway, the data need not be synced, the volatile keyword makes the boot faster, by not demanding sync. Tested on Raspberry Pi 4. Signed-off-by: Eric Curtin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM |
initoverlayfs is designed to be throwaway, the data need not be synced, the volatile keyword makes the boot faster, by not demanding sync. Tested on Raspberry Pi 4.