log2ram

Have got the same doubt, on OMV 5. I'm using a NanoPi Neo 2 with nas bay kit

At the moment, I left it unmounted and the system is fine.

I am currently looking into ram logging on my rock64 running Armbian 5.4 Buster.

Armbian uses armbian-ramlog that I think uses log2ram

The OMV config I use has the folder2ram plugin enabled. I'm not sure both are needed and I have issues with logrotate at the moment.

I have disabled armbian-ramlog and will see how things work over the next couple of days and report back.

Is your NanoPi running armbian?

I use NanoPi M4 (Debian Buster with Armbian Linux 4.4.192-rk3399), the distribution of the memory looks like this:

~# df -h
Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
udev            1,9G       0  1,9G    0% /dev
tmpfs           382M     13M  370M    4% /run
/dev/mmcblk1p1   15G    3,7G  9,7G   28% /
tmpfs           1,9G     20K  1,9G    1% /dev/shm
tmpfs           5,0M    8,0K  5,0M    1% /run/lock
tmpfs           1,9G       0  1,9G    0% /sys/fs/cgroup
tmpfs           1,9G    4,0K  1,9G    1% /tmp
/dev/zram0       49M    4,6M   41M   11% /var/log
folder2ram      1,9G       0  1,9G    0% /var/tmp
folder2ram      1,9G     12M  1,9G    1% /var/log.hdd
folder2ram      1,9G    644K  1,9G    1% /var/lib/openmediavault/rrd
folder2ram      1,9G    844K  1,9G    1% /var/spool
folder2ram      1,9G    579M  1,3G   31% /var/lib/rrdcached
/dev/sda1       3,7T    1,6T  2,1T   44% /export/RAID
folder2ram      1,9G    4,0K  1,9G    1% /var/lib/monit
folder2ram      1,9G    552K  1,9G    1% /var/cache/samba
/dev/sdb1       3,7T    1,1T  2,7T   29% /sharedfolders/Backups
overlay          15G    3,7G  9,7G   28% /var/lib/docker/overlay2/d61f0ccda...[...]

~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    1  3,7T  0 disk
└─sda1         8:1    1  3,7T  0 part /export/RAID
sdb            8:16   0  3,7T  0 disk
└─sdb1         8:17   0  3,7T  0 part /sharedfolders/Backups
mmcblk1      179:0    0 14,6G  0 disk
└─mmcblk1p1  179:1    0 14,4G  0 part /
mmcblk1boot0 179:32   0    4M  1 disk
mmcblk1boot1 179:64   0    4M  1 disk
mmcblk1rpmb  179:96   0    4M  0 disk
zram0        251:0    0   50M  0 disk /var/log
zram1        251:1    0  1,9G  0 disk [SWAP]

ryecoaaron I use the install script and I don't think it is disabling armbian-ramlog. On rock64 buster with kernel 5.4 it is not disabling and I have done around 5 clean installs over the last month or so. I'm using the script below.

https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash

I noticed this issue and after a bit of investigating, I have disabled armbian-ramlog manually and logrotate is working fine now.

forgot to say that I used this thread to work out how to disable ramlog

https://forum.armbian.com/topi…an-ram-logging-correctly/

In summary, I did the following and then did a reboot

systemctl disable armbian-ramlog

systemctl disable armbian-zram-config

changed the enabled flag to false in etc/default/armbian-ramlog

changed the enabled flag to false in etc/default/armbian-zram-config

commented out all lines in etc/cron.daily/armbian-ram-logging

Strange that the service does run on my clean install(s) of Armbian rock64 with OMV script. I am using latest Buster 5.4 image from the armbian website.

Have you done a install using latest build?

It is all fine now as I have disabled manually but it could affect others so I thought I would report it here.

all good. thanks for the help.

Any chance you can help with my last outstanding issue? see thread below

RE: FTP service running when disabled after reboot

Zitat von ryecoaaron

Disabling the service means the value in the default files doesn't matter.

I changed the values back to enabled in the default files and rebooted. After reboot the services do not start (as expected) but the armbian-ramlog does execute logrotate and this prevents OMV logrotate from working.

Changed the enabled setting back to disabled and rebooted. Now everything fine again. So long story short is that you do need to do all of the following to fully disable armbian-ramlog

systemctl disable armbian-ramlog

systemctl disable armbian-zram-config

changed the enabled flag to false in etc/default/armbian-ramlog

changed the enabled flag to false in etc/default/armbian-zram-config

commented out all lines in etc/cron.daily/armbian-ram-logging

have you made all the changes outlined in the previous post and restarted?

I already had this cron file commented out but it still ran armbian-ramlog

The only thing that I have found to stop it is to change the enabled flag in the default files below...

changed the enabled flag to false in etc/default/armbian-ramlog

changed the enabled flag to false in etc/default/armbian-zram-config

Understood. I have no idea what else could be triggering ambian-ramlog but something is and, therefore, the issue will persist for armbian builds.

I'm just a noob with enough knowledge to be dangerous but happy to help if I can. Sorry if I am not being helpful.

Awesome. thanks for your help with this.

Hello ryecoaaron,

I'm using Ordoid XU4 (Raspbian). I installed a new fresh system today with OMV on top of it with your installation script. And now I don't have any /dev/zram device and also don't have any swap anymore. Went through latest changes and find that topic. Is it an expected behavior?

root@odroidxu4:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    0  5.5T  0 disk 
mmcblk0      179:0    0 29.1G  0 disk 
└─mmcblk0p1  179:1    0 28.8G  0 part /
mmcblk0boot0 179:16   0    4M  1 disk 
mmcblk0boot1 179:32   0    4M  1 disk 

root@odroidxu4:~# free
              total        used        free      shared  buff/cache   available
Mem:        2043820      191824     1533760       28384      318236     1761480
Swap:             0           0           0