This page provides an introduction to swap space and paging on GNU/Linux. It covers creation and activation of swap partitions and swap files.
- Linux divides its physical RAM (random access memory) into chunks of memory called pages. Swapping is the process whereby a page of memory is copied to the preconfigured space on the hard disk, called swap space, to free up that page of memory. The combined sizes of the physical memory and the swap space is the amount of virtual memory available.
Support for swap is provided by the Linux kernel and user-space utilities from thepackage.
Swap space can take the form of a disk partition or a file. Users may create a swap space during installation or at any later time as desired. Swap space can be used for two purposes, to extend the virtual memory beyond the installed physical memory (RAM), and also for suspend-to-disk support.
If it is beneficial to extend the virtual memory with swap depends on the amount of installed physical memory. If the amount of physical memory is less than the amount of memory required to run all the desired programs, then it may be beneficial to enable swap. This avoids out of memory conditions, where the Linux kernel OOM killer mechanism will automatically attempt to free up memory by killing processes. To increase the amount of virtual memory to the required amount, add the necessary difference (or more) as swap space.
The biggest drawback of enabling swap is its lower performance, see section #Performance. Hence, enabling swap is a matter of personal preference: some prefer programs to be killed over enabling swap and others prefer enabling swap and slower system when the physical memory is exhausted.
To check swap status, use:
$ swapon --show
Or to show physical memory as well as swap usage:
$ free -h
A swap partition can be created with most GNU/Linux partitioning tools. Swap partitions are typically designated as type
82. Even though it is possible to use any partition type as swap, it is recommended to use type
82 in most cases since systemd will automatically detect it and mount it (see below).
To set up a partition as Linux swap area, thecommand is used. For example:
# mkswap /dev/sdxy
To enable the device for paging:
# swapon /dev/sdxy
To enable this swap partition on boot, add an entry to
UUID=device_UUID none swap defaults 0 0
device_UUID is the UUID of the swap space.
See fstab for the file syntax.
- The fstab-entry is optional if the swap partition is located on a device using GPT. See the next subsection.
- If using an SSD with TRIM support, consider using
discardin the swap line in fstab. If activating swap manually with swapon, using the
--discardparameter achieves the same. See for details.
Activation by systemd
systemd activates swap partitions based on two different mechanisms. Both are executables in
/usr/lib/systemd/system-generators. The generators are run on start-up and create native systemd units for mounts. The first,
systemd-fstab-generator, reads the fstab to generate units, including a unit for swap. The second,
systemd-gpt-auto-generator inspects the root disk to generate units. It operates on GPT disks only, and can identify swap partitions by their type GUID, see systemd#GPT partition automounting for more information.
To deactivate specific swap space:
# swapoff /dev/sdxy
Alternatively use the
-a switch to deactivate all swap space.
Since swap is managed by systemd, it will be activated again on the next system startup. To disable the automatic activation of detected swap space permanently, run
systemctl --type swap to find the responsible .swap unit and mask it.
As an alternative to creating an entire partition, a swap file offers the ability to vary its size on-the-fly, and is more easily removed altogether. This may be especially desirable if disk space is at a premium (e.g. a modestly-sized SSD).
Swap file creation
Use dd to create a swap file the size of your choosing. For example, creating a 512 MiB swap file:
# dd if=/dev/zero of=/swapfile bs=1M count=512 status=progress
Set the right permissions (a world-readable swap file is a huge local vulnerability):
# chmod 600 /swapfile
After creating the correctly sized file, format it to swap:
# mkswap /swapfile
Activate the swap file:
# swapon /swapfile
Finally, edit the fstab configuration to add an entry for the swap file:
/swapfile none swap defaults 0 0
For additional information, see fstab#Usage.
- The swap file must be specified by its location on the file system, not by its UUID or LABEL.
- When using Btrfs, do not forget to add the created subvolume to the list as well, and remove the
discard,autodefragand compression options.
Remove swap file
To remove a swap file, it must be turned off first and then can be removed:
# swapoff /swapfile # rm -f /swapfile
Finally remove the relevant entry from
The aim of this tool is the creation of zram devices. It is written in Rust and resides in systemd's GitHub. It can be installed with the package. Configuration is straightforward and explained in the README.
systemd-swap is a script for creating hybrid swap space from zram swaps, swap files and swap partitions. It is not affiliated with the systemd project.
- If the journal keeps showing the following warning
systemd-swap[..]: WARN: swapFC: ENOSPCand no swap file is being created, you need to uncomment and set
- The swap file created by systemd-swap cannot be easily used for hibernation. See systemd-swap issue 85.
Swap operations are usually significantly slower than directly accessing data in RAM. Disabling swap entirely to improve performance can sometimes lead to a degradation, since it decreases the memory available for VFS caches, causing more frequent and costly disk I/O.
Swap values can be adjusted to help performance:
The swappiness sysctl parameter represents the kernel's preference (or avoidance) of swap space. Swappiness can have a value between 0 and 200 (max 100 if Linux < 5.8), the default value is 60. A low value causes the kernel to avoid swapping, a high value causes the kernel to try to use swap space, and a value of 100 means IO cost is assumed to be equal. Using a low value on sufficient memory is known to improve responsiveness on many systems.
To check the current swappiness value:
$ sysctl vm.swappiness
Alternatively, the files
/proc/sys/vm/swappiness can be read in order to obtain the raw integer value.
/procis a lot less organized and is kept only for compatibility purposes, you are encouraged to use
To temporarily set the swappiness value:
# sysctl -w vm.swappiness=10
To set the swappiness value permanently, create aconfiguration file. For example:
To test and more on why this may work, take a look at this article.
VFS cache pressure
Another sysctl parameter that affects swap performance is
vm.vfs_cache_pressure, which controls the tendency of the kernel to reclaim the memory which is used for caching of VFS caches, versus pagecache and swap. Increasing this value increases the rate at which VFS caches are reclaimed. For more information, see the Linux kernel documentation.
If you have more than one swap file or swap partition you should consider assigning a priority value (0 to 32767) for each swap area. The system will use swap areas of higher priority before using swap areas of lower priority. For example, if you have a faster disk (
/dev/sda) and a slower disk (
/dev/sdb), assign a higher priority to the swap area located on the fastest device. Priorities can be assigned in fstab via the
/dev/sda1 none swap defaults,pri=100 0 0 /dev/sdb2 none swap defaults,pri=10 0 0
Or via the
--priority parameter of swapon:
# swapon --priority 100 /dev/sda1
If two or more areas have the same priority, and it is the highest priority available, pages are allocated on a round-robin basis between them.
Using zswap or zram
Zswap is a Linux kernel feature providing a compressed write-back cache for swapped pages. This increases the performance and decreases the IO-Operations. ZRAM creates a virtual compressed Swap-file in memory as alternative to a swapfile on disk.
There is no necessity to use RAID for swap performance reasons. The kernel itself can stripe swapping on several devices, if you just give them the same priority in the
/etc/fstab file. Refer to The Software-RAID HOWTO for details.