How to disable properly swap partition?

Hi there,
Back in the OMV5 days I recall that the flasmemory plugin advised to disable swap and that's what I did back then.

OMV6 flasmemory plugin does not give any advice, but I realized I have a swap partition that is running off my USB stick, and I believe this is the cause of the slowdowns I'm facing.

How do I permanently disable the swap partition?

I already edited /etc/fstab to comment out the swap partition and executed swapoff /dev/sdXY with the correct partition. On the fly the swap partition is emptied and disabled, but after a reboot the swap is enabled again.

There must be a salt config or some other default that is turning it on again, can you assist?

I'm surprised that nobody has reported this before, but what's the point of using the flashmemory plugin if the swap partition is kept on by default on the same usb flash drive we're trying to preserve?

I could re-enable swap by using swapfile on my NVMe drive used for apps and docker, but let's do one step at the time.

Posting here to provide an update.

I ended up not disabling swap, but switching to swapfile on another drive.

It's fairly easy to setup and does not require formatting or creating a partition.

In this example, I created a 4GB swapfile. Use an SSD if you can, you can store the file anywhere on the disk, I did in the root.

These steps are only for x86/64 systems

• Check the current swap configuration by running swapon -s
• Execute the following commands to create the swapfile, assign the right permissions and enable it to be a swapfile

fallocate -l 4G /path/to/swapfile
chmod 600 /path/to/swapfile
mkswap /path/to/swapfile
swapon /path/to/swapfile

• Edit fstab with your favorite editor, like nano /etc/fstab

• Comment out the existing swap partition

• Add the new swap file like this:

/path/to/swapfile none swap sw 0 0

• Restart the OS

• Check that the file has replaced the previous partition by executing swapon -s

Quote from Soma

an you also make a small mention to what architecture this applies?

In my signature I have listed my hardware, so my experience as this procedure is limited to x86/64.

I hoping I'm not the only one running OMV on a thumbdrive with an x86/64 system

Quote from Soma

Most of the time, i'm on phone and am unable to see signatures, 😉

No problem, I updated the post mentioning it's only for x86/64.

I never pretended to make a full guide, but just describe what I did.

Quote from ryecoaaron

I do. And the swap is still on the thumb drive : )

You must be crazy, or just have lots of ram

ryecoaaron I've checked my machine and I have no files under /etc/initramfs-tools/conf.d/

My real machine is a UEFI install, while my OMV VM I use for testing has such file, but has a Legacy BIOS.

Another cause could be that I disabled hybernation on the real machine by running systemctl mask hibernate.target ?

I don't know what resume file is used form, but it's missing.

Quote from ryecoaaron

Not sure. I don't have a real machine I want to test this on.

Fine, I won't dig deeper. After all the OS is not complaining about that.

I think that if doesn't exist you're fine.