Clear Linux OS uses 480 MB on an 16Go encrypted swap partition initially created for AlmaLinux OS

General Discussion
1

Hi,

I’ve an installation with encrypted partitions for Data, and 3 distros, the last one is Clear Linux OS
Clear Linux OS was installed with the safe installation option and 64MB /var swap and wanted to add an extra 7.9Go encrypted swap partition for CLR_SWAP, but …

During the start-up procedure luks asks me for :

  1. The passphrase of / ( CLR root )
  2. The passphrase of alma-swap ( 16Go encrypted partition used for AlmaLinux OS )

Clear Linux OS detects and uses well the swap 16Go partition , I changed the size of swap to 14Go just to be sure it is really reconized ( manual Swap Off, Resize, close Encryption, move right the partition, open Encryption, manual Swap On ) and reversed to 16Go … Both sizes detected well and still running ok…

Clear Linux OS used up to 480 MB of this 16Go partition swap Partition during swupd repair…
( swupd said : ‘3965 of 3965 missing files were replaced’ )

ALMALINUX_SWAP_USED_MY_PARTITIONS_2022-07-24-15-20-05
ALMALINUX_SWAP_USED_MY_PARTITIONS_2022-07-24-15-20-051310×571 96.7 KB

ALMALINUX_SWAP_USED_450M_BY_CLR_2022-07-24-15-19-07
ALMALINUX_SWAP_USED_450M_BY_CLR_2022-07-24-15-19-071920×1080 166 KB

I’m just wondering :

  • How can Clear Linux OS detect the type of an encrypted swap parition ? or is it only looking at parition name ?
  • Why installing by default an /var swap file small ( 64 MB ) as Clear Linux OS used up to 480 MB just for a check/repair ?
  • What are the risks of having an swap partition bigger than 8 Go ?

If somebody can help…

Best regards,
ClearLinux.User.809

1 Like
2

Can be done on the fly in terminal then re-boot I re-sized my swap from 64MiB to 2GiB on an old HP Stream 13 with only 2 Gigs of RAM runs nice and smooth now.
sudo swapoff /var/swapfile
sudo dd if=/dev/zero of=/var/swapfile bs=64MiB count=2GiB
sudo mkswap /var/swapfile
sudo chmod 0600 /var/swapfile
sudo swapon /var/swapfile

1 Like
3

By partition type. Swap is ‘0657fd6d-a4ab-43c4-84e5-0933c84b4f4f’.
Try “lsblk --output +PARTTYPE,PARTTYPENAME”.

1 Like
4

Thanks for the info !