subprocess.CalledProcessError: Command '['systemctl', 'start', 'var-lib-systemd\x2dswap-swapfc-x.swap']' returned non-zero exit status 1. #194
Comments
|
I'd recommend keeping the default |
|
ok, i used the config from https://github.com/Nefelim4ag/systemd-swap/blob/master/include/swap-default.conf and only set |
|
ok, now it seems to be working correclty - i didn't change anything, so it has to be something in manjaros testing-update from the 22nd: https://lists.manjaro.org/pipermail/manjaro-packages/Week-of-Mon-20201221/034718.html |
|
apparently it's still present, just much later: ~ >>> systemctl status systemd-swap.service Dez 27 01:36:53 Zaubertrank systemd-swap[1370]: swap_fc.run() |
Termuellinator
changed the title
Termuellinator
changed the title
|
Please provide the the error message ( |
not very much... i've also tried some other numbers (swapfc-1.swap, swapfc-8.swap and so on), no entries for any of them
|
|
i've observed it the last couple days and the error still appears on swapfc-1.swap most of the times :/ |
|
You could manually use the bash branch (4.3.x) for now (you should probably just be able to just replace /usr/bin/systemd-swap with the bash version), development has stalled on the python branch since I've stopped using it. I do plan on ramping up development come summer |
|
oh, i wasn't aware of the rewrite - i've downgraded to 4.3.3 and will keep you posted! May i ask how you setup your swap now if you stopped using you script here? For me, it seems like the most elegant way i've found yet :) |
|
I only use zram so this is enough https://github.com/systemd/zram-generator |
|
Same issue observed here, with exactly the same swap chunk number. Log from both systemd units: In the log, it looks like the same swap chunk failed on a previous boot as well. |
|
There is a kernel limit for the amount of active swap files. Should be 32 and it seems like additional limitations imposed by some kernel configuration options can bring that down to 27 (https://unix.stackexchange.com/a/638358). That would explain why the exact number of swap files when it fails is 28. We should probably update the default settings accordingly. |
Hi, i recently switched to btrfs and now have issues getting systemd-swap to work properly.
It starts up fine but once i open a more memory intensive program, i don't see any swap being used in the ressource monitor and the service failed:
My config:
i've created an @swap subvolume that is mounted at /swap , in there i created a folder swapfc and did
sudo btrfs property set /swap/swapfc compression noneandsudo chattr +C /swap/swapfcWhen the systemd-swap.service is started everything looks fine, the folder /swap/swapfc is empty. When i notice the stopped service there is a file named "1" in that folder that is deleted when i systemctl stop systemd-swap.service.
I'm not sure what i'm doing wrong - it seems the program is trying to un-set CoW for the file and fails? Could it be that me setting chattr +C for the folder is wrong because the file already inherits the flag on creation?
The text was updated successfully, but these errors were encountered: