Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#53219 - [systemd-swap] Chunk swapfiles are not created on swapless system
Attached to Project:
Community Packages
Opened by Scott Burman (osteichthyes) - Wednesday, 08 March 2017, 21:41 GMT
Last edited by Ivy Foster (escondida) - Thursday, 10 October 2019, 21:45 GMT
Opened by Scott Burman (osteichthyes) - Wednesday, 08 March 2017, 21:41 GMT
Last edited by Ivy Foster (escondida) - Thursday, 10 October 2019, 21:45 GMT
|
DetailsDescription:
Because the chunk generation is triggered by the swap falling below 15% (or whatever is configured in the config), a system with no other swap will always have 0% full, so the first chunks is never created. I worked around this by simply creating a small swap file (~10M), which is trivial from a swapping standpoint, but that way when it is <15% empty, the first chunk is generated. You could easily add a similar function to systemd-swap, to allocate a 10M swapfile, further, it could be a simple config option so folks with an actual swap partition could skip it. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Use any system with no swap. |
This task depends upon
Closed by Ivy Foster (escondida)
Thursday, 10 October 2019, 21:45 GMT
Reason for closing: Upstream
Additional comments about closing: As felixonmars pointed out, this behavior should be fixed upstream, if anywhere.
Thursday, 10 October 2019, 21:45 GMT
Reason for closing: Upstream
Additional comments about closing: As felixonmars pointed out, this behavior should be fixed upstream, if anywhere.
Comment by Felix Yan (felixonmars) -
Sunday, 09 July 2017, 15:36 GMT
Did you report this to the upstream developer? I assume this is not a packaging fault...