I'm too spoiled by configuration management. I know we tell ansible and puppet at work to set it swappiness to 0 and it will be set there. I just don't pay attention to as much at home unless there is a problem.
On my primary server, I just disabled swap to drain it, made sure swappiness is 0, and the enabled swap again. We will see how it acts now.
I know, the most people don´t care about RAM memory anymore, because they have plenty of it
When I write code, I still optimize it to use as little ram as possible. I remember the 640k days spending lots of time optimizing config.sys to get everything in highmem. No swap back then.
I remember the 640k days spending lots of time optimizing config.sys to get everything in highmem.
Oh that's a blast from the past! 
Do you have any idea where the swappiness 150 is coming from?
The plugin is defaulting the zram swap to 150 at the suggestion of zram-config.
Is this setting a good idea???
It isn't horrible. You are moving things in ram to compressed zram. So, your system should use less ram and might even be a bit faster when accessing the data in the zram swap.
The defaults may not be perfect for my 4GB machine.
Depends on what you are doing on it. They are just fine on my 8gb rpi. I would just delete the swap from the plugin if you think it isn't going to work but I don't understand why swapping ram to compressed ram wouldn't work on any system.
The plugin has to have defaults. I made them editable so people can change them.
First of all, i try to understand the settings of your new plugin... What is the limit doing?
From the zram-config page:
Quotemem_limit is the compressed memory limit and will set a hard memory limit for the system admin. Set to 0 to disable the mem_limit.
Quotedisk_size is the maximum size of the uncompressed memory. It should be set to roughly 150% of mem_limit depending on the algorithm and how compressible the input files are. Don't make it much higher than the compression algorithm (and the additional zram overhead) is capable of because there is a ~0.1% memory overhead when empty.
With the old plugin there was nothing to configure and think about...
folder2ram used tmpfs for everything and it is defaulted to use half of the system's ram. if there isn't enough ram, it pushes some things to swap.
zram-config creates a zram block device for each item in the list of the plugin. It has to have a size just like tmpfs.
You don't have to think about anything. You can use default settings just like many other things in OMV. I don't know how to make the plugin satisfy people who want to configure things and people who don't want to configure things.
All I can tell you is that my five systems the new version is running on aren't having problems.
Hi Aaron
I don't know how to make the plugin satisfy people who want to configure things and people who don't want to configure things.
I´m not complaining about anything... It´s fine!!
At this morning i got following error during system booting:
root@pr-srv-01:~# journalctl -b
.........
Mär 16 07:50:26 pr-srv-01 logrotate[757]: error: failed to rename /usr/local/share/zram-config/log/zram-config.log to /usr/local/sh>
Mär 16 07:50:26 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Mär 16 07:50:26 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.
Mär 16 07:50:26 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.
Mär 16 07:50:26 pr-srv-01 smbd[792]: [2025/03/16 07:50:26.345854, 0] ../../source3/smbd/server.c:1741(main)
Mär 16 07:50:26 pr-srv-01 smbd[792]: smbd version 4.17.12-Debian started.
Mär 16 07:50:26 pr-srv-01 smbd[792]: Copyright Andrew Tridgell and the Samba Team 1992-2022
.........
root@pr-srv-01:~# journalctl -u logrotate -b
Mär 16 07:50:24 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...
Mär 16 07:50:26 pr-srv-01 logrotate[757]: error: failed to rename /usr/local/share/zram-config/log/zram-config.log to /usr/local/sh>
Mär 16 07:50:26 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Mär 16 07:50:26 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.
Mär 16 07:50:26 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.
root@pr-srv-01:~# journalctl -b|grep fail
Mär 16 07:50:26 pr-srv-01 logrotate[757]: error: failed to rename /usr/local/share/zram-config/log/zram-config.log to /usr/local/share/zram-config/log/zram-config.log.tmp: Das Dateisystem ist nur lesbar
(Filesystem only readable??)
Any ideas why this is happening?
By the way, a stupid question:
"disk_size is the maximum size of the uncompressed memory. It should be set to roughly 150% of mem_limit....."
Your defaults of your new flashmemory plugin are exceeding this advice...
No idea, if this will leading to any problems....
Best regards
prtigger
I can confirm this although the system was running 24/7:
$ sudo systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● logrotate.service loaded failed failed Rotate log files
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
$ sudo systemctl status logrotate.service
× logrotate.service - Rotate log files
Loaded: loaded (/lib/systemd/system/logrotate.service; static)
Active: failed (Result: exit-code) since Sun 2025-03-16 00:00:04 WET; 8h ago
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Process: 3752188 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
Main PID: 3752188 (code=exited, status=1/FAILURE)
CPU: 261ms
Mar 16 00:00:02 panela systemd[1]: Starting logrotate.service - Rotate log files...
Mar 16 00:00:04 panela logrotate[3752188]: error: failed to rename /usr/local/share/zram-config/log/zram-config.log to /usr/local/share/zram-config/log/zram-config.log.tmp: Read-only file system
Mar 16 00:00:04 panela systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Mar 16 00:00:04 panela systemd[1]: logrotate.service: Failed with result 'exit-code'.
Mar 16 00:00:04 panela systemd[1]: Failed to start logrotate.service - Rotate log files.
$ sudo systemctl restart logrotate.service
$ sudo systemctl status logrotate.service
○ logrotate.service - Rotate log files
Loaded: loaded (/lib/systemd/system/logrotate.service; static)
Active: inactive (dead) since Sun 2025-03-16 08:04:15 WET; 2s ago
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Process: 3809104 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=0/SUCCESS)
Main PID: 3809104 (code=exited, status=0/SUCCESS)
CPU: 112ms
Mar 16 08:04:14 panela systemd[1]: Starting logrotate.service - Rotate log files...
Mar 16 08:04:15 panela systemd[1]: logrotate.service: Deactivated successfully.
Mar 16 08:04:15 panela systemd[1]: Finished logrotate.service - Rotate log files.After restarting the service, it started clean.
Seems to be the same like here:
https://support.hpe.com/hpesc/public/docDisplay?docId=c03731635&docLocale=en_US
My system is not HP, but i guess it´s the same problem. No support of ERST feature..
No BIOS anymore for my very old system (Last one from 2013).
I don´t know, why these error coming up at this time, because i never had them before.
Question:
Does anyone knows, if there is a way to reset this with the Linux OS....
nginx.service is still fireing error during boot....
This may happenn because i try to uninstall the flashmemoryplugin with:
sudo apt-get purge openmediavault-flashmemory
That wasn´t working correct.... Maybe i crashed something
Best regards
prtigger
Any ideas why this is happening?
logrotate is failing to rotate the zram-config log. I just used the zram-config supplied logrotate file. Not sure why it is read only. I will have to look into it more.
Your defaults of your new flashmemory plugin are exceeding this advice...
No idea, if this will leading to any problems....
If you look at the example config on the zram-config page, I used their example sizes. I haven't seen any problems.
Now i've got problems during boot.. I got errors displayed, i never had before...
These aren't related to flashmemory/zram-config.
After uninstalling flashmemory testing version i got problems with nginx.service startup again...
Did you run omv-salt deploy run nginx? Seems like the most common problem is /var/log/nginx doesn't get created.
This may happenn because i try to uninstall the flashmemoryplugin with:
sudo apt-get purge openmediavault-flashmemory
That wasn´t working correct
That is how I would uninstall it but I rarely uninstall the plugin. What wasn't working correct about the uninstall other than the nginx issue?
Mär 16 09:57:57 pr-srv-01 kernel: ERST: Failed to get Error Log Address Range.
......
Mär 16 09:57:57 pr-srv-01 kernel: APEI: Can not request [mem 0xbff9a740-0xbff9a793] for APEI BERT registers
Hi Aaron
Yes, this is a Linux problem.
My knowledge is not high enough for
finding a solution, clearing the error...
At this time it's coming at every boot.
BIOS Setup is cleared and restored...
May someone knows what to do??
Did you run omv-salt deploy run nginx? Seems like the most common problem is /var/log/nginx doesn't get created.
Is that the ony command i have to use on console?
Best regards
prtigger
Display MoreYes, this is a Linux problem.
My knowledge is not high enough for
finding a solution, clearing the error...
At this time it's coming at every boot.
BIOS Setup is cleared and restored...
May someone knows what to do??
I was trying not to get off topic. Both "errors" are acpi related and should be safe to ignore. If they bother you, I'm sure chatgpt can explain how to disable them.
Is that the ony command i have to use on console?
I don't know why nginx isn't starting since I can't see any logs. So, omv-salt deploy run nginx is the first command I would run. If it fixes, great. If not, we need logs to know what to do next. Using systemctl status nginx tells you enough to fix it.
I don't know why nginx isn't starting since I can't see any logs. So, omv-salt deploy run nginx is the first command I would run. If it fixes, great. If not, we need logs to know what to do next. Using systemctl status nginx tells you enough to fix it.
deploy run nginx was showing errors...
Because /var/log/nginx was missing.
Created it and done command again
fixed the problem, so i can use GUI again.
Now i have to install one of your flashmemory plugins again...
Best regards
prtigger
Don’t have an account yet? Register yourself now and be a part of our community!
