
I don't understand why lvm.log is placed in /tmp directory without rotation. I noticed this fact when I got the following event notification every 2 hours. EventID :24 Message :Critical, Low disk space. Host ovirt01 has less than 500 MB of free space left on: /tmp. Low disk space might cause an issue upgrading this host. As a workaround, I added a log rotation setting to /tmp/lvm.log, but is this the correct way? I should have understood the contents of the Python program below before asking the question, but please forgive me because I am not very knowledgeable about Python. # cat /usr/lib/python3.6/site-packages/blivet/devicelibs/lvm.py | grep lvm.log config_string += "log {level=7 file=/tmp/lvm.log syslog=0}" Thanks in advance!! Further information is below [root@ovirt01 ~]# cat /etc/os-release NAME="CentOS Stream" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8.7.2206.0" VARIANT="oVirt Node 4.5.4" VARIANT_ID="ovirt-node" PRETTY_NAME="oVirt Node 4.5.4" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://www.ovirt.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" PLATFORM_ID="platform:el8" [root@ovirt01 ~]# uname -a Linux ovirt01 4.18.0-408.el8.x86_64 #1 SMP Mon Jul 18 17:42:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux [root@ovirt01 ~]# df -h | grep -E " /tmp|Filesystem" Filesystem Size Used Avail Use% Mounted on /dev/mapper/onn_ovirt01-tmp 1014M 515M 499M 51% /tmp [root@ovirt01 ~]# stat /tmp/lvm.log File: /tmp/lvm.log Size: 463915707 Blocks: 906088 IO Block: 4096 regular file Device: fd0eh/64782d Inode: 137 Links: 1 Access: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ root) Context: system_u:object_r:lvm_tmp_t:s0 Access: 2023-02-03 10:30:06.605936740 +0900 Modify: 2023-02-03 09:52:19.712301285 +0900 Change: 2023-02-03 09:52:19.712301285 +0900 Birth: 2023-01-16 01:06:02.768495837 +0900

Hi I have the exact same issue. Did you just add an entry in /etc/logrotate.d/ or did you solve it in a different way? Regards, Jonas
participants (2)
-
jonas@rabe.ch
-
kanehisa@ktcsp.net