-
Notifications
You must be signed in to change notification settings - Fork 55
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
zvol for swap and sync=? #229
Comments
Ping. Any response? |
|
My guess: I assume the reasoning here is that if we are under a condition of extreme memory pressure (e.g. swapping is required) then it doesn't make sense to use more memory to buffer these writes which would compound the problem |
|
Actually I've also just stumpled over that. I've wanted to checkout what are recommended settings for swap devices, and noticed, that everybody recommends sync=always (but their commands look al the same, so I guess they've all copied from the same place). Could anybody with more insight tell if there is any reason why sync=always should be used than sync=disabled (Which seems to be the logical choice for me) |
Looking in:
https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-use-a-zvol-as-a-swap-device
I see
why
sync=always
? if the system crashes all RAM will be lost. hence writing swap synchronously seems a bit too much.FreeBSD docs for reference:
https://wiki.freebsd.org/RootOnZFS#ZFS_Swap_Volume
Why should it be
sync=always
when using zfs on linux, or is it a typo?The text was updated successfully, but these errors were encountered: