kevkkvek

I'm ok but I just don't want to have any performance problems. Before zram0 was mounted in /var/log. What happens with the logs now.? This box is mainly for servers.

######before zram-confing ~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 24G 0 part / ├─sda2 8:2 0 16G 0 part [SWAP] └─sda3 8:3 0 891.5G 0 part /opt mtdblock0 31:0 0 4M 0 disk zram0 252:0 0 50M 0 disk /var/log zram1 252:1 0 2G 0 disk [SWAP] ######after zram-config ~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 24G 0 part / ├─sda2 8:2 0 16G 0 part [SWAP] └─sda3 8:3 0 891.5G 0 part /opt mtdblock0 31:0 0 4M 0 disk zram0 252:0 0 498.6M 0 disk [SWAP] zram1 252:1 0 498.6M 0 disk [SWAP] zram2 252:2 0 498.6M 0 disk [SWAP] zram3 252:3 0 498.6M 0 disk [SWAP] how do i make it back as it was?

Yeah, did that. BTW, the zram-config tool wasn't installed by default on my system. is that normal or ...strange?

Sorry for asking but how do you reinstall zram-config? ~sudo apt install zram-config"? Is there any danger in doing that? I can't say i'm a linux guru by any means. I would also like to do something about the logging because nginx also gives me full zram messages all the time.

I think this should be it, hope you can take a look at my armbianmonitor -u: http://ix.io/1MXs

I am getting a series of errors related to EXT4 zram checksum that look like this one: [3328.749555] EXT4-fs error (device zram0): ext4_readdir:189: inode #11 com find: path var/log/lost+found directory fails checksum at offset 4096 (and other offsets) I've seen a recommendation as a possible fix to the checksum error : disabling metadata_csum, using "tune2fs -O ^metadata_csum /dev/zram0", with the file system umounted (I don't know how to unmount zram) The error apparently is related to bad hardware (not the case) , old kernels that don't support new versions of programs capable of altering the fs. Like a newer checksum feature, or a new e2fsprogs. Would appreciate some help. Thx.