On 2024-02-17 22:10, -pj via openSUSE Users wrote:
On 02-17-2024 02:26PM, Carlos E. R. wrote:
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:
...
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.
Ok, very good advice. I passed the following commands:
# swapoff -a - # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap - # swapon /dev/system/swap
This is 'free -m' output now after powercycle:
# free -m total used free shared buff/cache available Mem: 7693 3067 2851 63 2163 4625 Swap: 15887 1828 14059
I believe swap is working again. Are you aware of any other testing to ensure that swap is working?
Just that you see it in "used". Yes, there are other commands, for instance: Telcontar:~ # swapon NAME TYPE SIZE USED PRIO /dev/nvme0n1p2 partition 100G 696.5M -2 Telcontar:~ # (I haven't hibernated after booting a while ago). Try "swapon -s". Top is another command, which also displays swap among many other things. Oh, by the way, I pass "-h" to free. I like to see the units :-)
Another question for you is that currently attempting to 'Hibernate' (tried twice), the machine goes through the process...halts/poweroff completely for about a second. Then powers up in a poweron at bios where after entering the LUKS passphrase some boot information is displayed. Is it best to start a new post about this?
Yep. It really powers down, stops fans and all leds? Then starts on its own? Weird day you have. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)