On 30/11/2018 20:40, Tim wrote:
On 30/11/2018 19:17, Ian Morris wrote:
Did you format the partition with mkswap first? Used to be that this was
mandatory but I'm not sure if it sill is because it's been a very long
time since I did this manually...
It could explain why the kernel stops using it unexpectedly though ....
On 30/11/2018 14:22, Tim wrote:
I am running a Debian testing based distro on my PC which has three
hard disk in it SDA, SDB & SDC and their layout was as follows:
SDA
sda1 fat32 /boot/efi
sda2 ext4 /
sda3 ext /home
sda4 swap
SDB
unpartitioned
SDC
sdc1 ext4 /media/backup
I decided to move the swap file from sda to a new swap partition I
made on sdb which was set up as sdb1 (made the swap file with gparted,
10gb same size as the one on sda) .
I turned swap off
I edited the fstab file and entered the new uuid for the swap file on
sdb1 then turned swap back on again.
I can see the swap file is on and being used (below a couple of
minutes after a reboot hence the low usage) and as I use the PC during
the day I see the amount of swap usage increase.
|mit@andora:~$ free -m total used free shared buff/cache available
Mem: 7687 4117 942 519 2626 2781 Swap: 9999 3 9996 |
Now since making the change every morning when I come down to my PC
both my open web browsers will have crashed and swap is turned off
(nothing is programmed to run in browsers overnight), I did not have
this issue when swap was on sda4 I simply do sudo swapon -a in the
morning and the swap file is back up and running.
I have had a look in my log but to be honest I am not sure what log to
look at, I have looked on line but was unable to see anything obvious.
Can anybody advise please?
Well for the sake of sanity I have just reformatted the swap file, so
we will see what happens
Tim
Yesterday I reformatted the swap file just encase there had been an
issue (as mentioned above) and then re-mounted it with out issue. This
morning I come to my PC to find that one browser had closed and the swap
was off. Tries to manually start swap and it complained that it could
not find the UUID. This turned out to be true as the UUID for sdb1 had
changed, but the question is when did it change? Yes I can see that
formatting the drive could force the drive to have a new UUID but if
that was the case how was I able to turn swap on yesterday after the
formatting it again, I did not change the UUID in fstab yesterday afternoon?
There was also a suggestion that the issue could be related to a
security update on intel based chips, so I will spend some time looking
at that later.
Tim
--
Next meeting at *new* venue: Bournemouth, Tuesday, 2018-12-04 20:00
Check if you're replying to the list or the author
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
