Time to time i got following notification on Banana Pi M1.  Only after reboot Banana starts working properly. How to tune zram to avoid such kind of issue? No tuning made till now

 

Linux bananapi 4.19.17-sunxi #5.73 SMP Mon Jan 28 21:06:40 CET 2019 armv7l GNU/Linux

 

 

error: Compressing program wrote following message to stderr when compressing log /var/log/letsencrypt/letsencrypt.log.1:

 

gzip: stdout: No space left on device

error: failed to compress log /var/log/letsencrypt/letsencrypt.log.1

error: Compressing program wrote following message to stderr when compressing log /var/log/wtmp.1:

 

gzip: stdout: No space left on device

error: failed to compress log /var/log/wtmp.1

error: Compressing program wrote following message to stderr when compressing log /var/log/btmp.1:

 

gzip: stdout: No space left on device

error: failed to compress log /var/log/btmp.1

/etc/default/armbian-zram-config 

 

# configuration values for the armbian-zram-config service
#
# enable the armbian-zram-config service?
ENABLED=true

# percentage of zram used as swap compared to physically available DRAM.
# Huge overcommitment (300) is possible and sometimes desirable. See
# https://forum.armbian.com/topic/5565-zram-vs-swap/?do=findComment&comment=61082
# and don't forget to adjust $MEM_LIMIT_PERCENTAGE below too.
# ZRAM_PERCENTAGE=50

# percentage of DRAM available to zram. If this amount is exceeded the zram
# devices used for swap simply behave as if the device is full. You need to
# adjust/increase this value only if you want to work with massive memory
# overcommitment (ZRAM_PERCENTAGE exceeding 150 for example)
# MEM_LIMIT_PERCENTAGE=50

# create how many zram devices max for swap
# ZRAM_MAX_DEVICES=4

# Which algorithm for zram based swapping. Seems lzo is best choice on ARM:
# https://forum.armbian.com/topic/8161-swap-on-sbc/?do=findComment&comment=61668
# SWAP_ALGORITHM=lzo

# Which algorithm to choose for zram based ramlog partition
# RAMLOG_ALGORITHM=zstd

# Which algorithm to choose for zram based /tmp
# TMP_ALGORITHM=zstd

 

and where can I define the size of RAMLOG in particular?

1 hour ago, Markus Rohner-Bührer said:

and where can I define the size of RAMLOG in particular?

/etc/default/armbian-ramlog

@AZ8 you could also check if your system actually has to the patch for journald log-size in /var/log: