I'm sorry, - my last posts duplicates; can somebody delete at least comment 45? (it will be a good idea, to make possible to edit or delete posts...)
Mr. Kennet Parker,
> It seems that the issue might be in the initial "guess" at the size of the Ram Disk, right?
I'm not sure, I am not specialist as you....
> "executive summary" of your last three posts, in Command Line System Admin language (as opposed to Kernel Hacker language)?
Sorry, I'm not a profi.... I try to more shortly:
last 4096 bites of /dev/zram0 seems to be broken; so, you need to check it after swapon (for example, by
# mkswap -c /dev/zram0
if you use zram-config, change in cat /etc/init/zram-config.conf line
mkswap /dev/zram${DEVNUMBER}
to
mkswap -c /dev/zram${DEVNUMBER}
#####
But anyway, software can "eat" your memory faster than kernel swapped it from RAM to /dev/zram....
I'm sorry, - my last posts duplicates; can somebody delete at least comment 45? (it will be a good idea, to make possible to edit or delete posts...)
Mr. Kennet Parker,
> It seems that the issue might be in the initial "guess" at the size of the Ram Disk, right?
I'm not sure, I am not specialist as you....
> "executive summary" of your last three posts, in Command Line System Admin language (as opposed to Kernel Hacker language)?
Sorry, I'm not a profi.... I try to more shortly:
last 4096 bites of /dev/zram0 seems to be broken; so, you need to check it after swapon (for example, by
# mkswap -c /dev/zram0
if you use zram-config, change in cat /etc/init/ zram-config. conf line
mkswap /dev/zram$ {DEVNUMBER}
to
mkswap -c /dev/zram$ {DEVNUMBER}
#####
But anyway, software can "eat" your memory faster than kernel swapped it from RAM to /dev/zram....