Opened 9 years ago

Last modified 7 years ago

#4843 assigned bug

Disabling VirtualMemory does not free up disk space

Reported by: Adek336 Owned by: leavengood
Priority: normal Milestone: R1
Component: Preferences/VirtualMemory Version: R1/Development
Keywords: Cc: hamish@…
Blocked By: Blocking:
Has a Patch: no Platform: All


hrev33753 gcc4+2 hybrid

Disable VirtualMemory, reboot, disk space still used by swap. Go to VirtualMemory preferences ; note that the size slider is not disabled. Anyhow, moving the slider to 1 MiB does not free up memory either. /boot/var/swap is still 2 GiB.

Removing the file frees up memory and doesn't introduce any problems or crashes.

Change History (6)

comment:1 Changed 9 years ago by mmadia

Version: R1/alpha1R1/Development

comment:2 Changed 8 years ago by leavengood

Owner: changed from axeld to leavengood
Status: newassigned

Taking ownership.

comment:3 Changed 8 years ago by leavengood

A user in IRC found this bug as well, but in his case deleting the file did not seem to actually free the disk space. Either way the system should remove or at least truncate to 0 the swap file when virtual memory is disabled.

I'll attempt to make the fix which does one or the other. It will be my first kernel change ;)

comment:4 Changed 8 years ago by hamish

The way you fix this is relevant to a patch I'm working on in #3723.

With support for swap on different volumes, simply deleting /var/swap at boot won't work. Also, deleting the swap file from the volume specified in the config won't work either, because the user could have changed the swap volume and rebooted, leaving a dormant swap file on the old volume.

I thought a possible solution might be to symlink /var/swap to wherever the swap file actually is, and delete through that at boot. This would require that the target volume be manually mounted and then unmounted for the deletion.

Ideally, there would be a procedure to switch off virtual mem at system shutdown which would make use of the existing swap_file_delete() function.

comment:5 Changed 8 years ago by hamish

Cc: hamish@… added

comment:6 Changed 7 years ago by kallisti5

#8971 opened to track the issue with the non-erased swap.

After the OS releases the swap, the file can be erased. (however, remember to empty the trash to regain the space!)

Note: See TracTickets for help on using tickets.