On 2024-02-17 20:58, -pj via openSUSE Users wrote:
On 02-17-2024 12:32PM, Carlos E. R. wrote:
On 2024-02-17 19:15, -pj via openSUSE Users wrote:
On 02-17-2024 12:02PM, Carlos E. R. wrote:
On 2024-02-17 18:37, -pj via openSUSE Users wrote:
On 02-17-2024 07:06AM, Carlos E. R. wrote:
On 2024-02-17 06:58, -pj via openSUSE Users wrote: > On 02-16-2024 11:21PM, Masaru Nomiya wrote:
>> [...] >>
...
7. Note how swap is now displayed at 15.5G in size.
Yes, I did.
Please note that 'free -m' output displays only what appears to be the previous swap size. I just noticed this.
Huh?
[...]
Right, you need to call "mkswap" on the device.
Disable swap, run mkswap on it, enable swap.
I am very glad you responded to this above. I have never done this before (enlarging swap).
I see in 'man swap' the following might accomplish this.
1. # swapoff -all - passing: lsblk -f -> system-swap swap 1 e736498b-60e5-4f99-99c2-8a6850a78ca9 [SWAP]
I see in 'man mkswap' the following may be what I am looking for to enlarge the actual swap file.
2. # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap -
Ah, good idea, keeping the uuid. In my case, as I use labels, I would have to try to keep it.
Then enable swap partition again.
3. # swapon /dev/system/swap - What will happen if no "uuid" is specified in mkswap?
A new random uuid is created. So if the uuid was specified in fstab or elsewhere, things stop working.
Does this look correct to you what I am considering to do above? I do not believe that a new uuid needs to be generated by default.
mkswap is a format; all format tools create things afresh. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)