Andrei Borzenkov composed on 2022-06-25 07:35 (UTC+0300):
Felix Miata wrote:
Apparently the problem is at least in part the immediate activation on a new boot, a boot on which a large quantity of transactions subsequently transpire from zypper dup after a lengthy period of no booting. It compacts the old file with the current date, then on a subsequent boot following a new kernel installation and massive zypper.log growth,
You seriously say that one zypper dup results in 10M log file?
# ls -gGh zypp* -rw-r----- 1 17M Jun 3 20:08 zypper.log -rw-r----- 1 799K Mar 30 19:08 zypper.log-20220603.xz zypp: total 4.9M -rw-rw-r-- 1 4.9M Jun 3 20:08 history # head -n2 zypper.log 2022-06-03 19:24:22 <1> <>(2140) [zypper] main.cc(main):125 ===== Hi, me zypper 1.14.52 2022-06-03 19:24:22 <1> <>(2140) [zypper] main.cc(main):126 ===== 'zypper' 'ref' ===== # tail -n2 zypper.log 2022-06-03 20:08:13 <1> <>(15102) [zypper] Zypper.cc(cleanup):729 START 2022-06-03 20:08:13 <1> <>(15102) [zypper] main.cc(~Bye):98 ===== Exiting main(0) ===== # grep zypper zypper.log | grep "'dup' '-d'" 2022-06-03 19:26:05 <1> <>(2426) [zypper] main.cc(main):126 ===== 'zypper' '-v' 'dup' '-d' ===== The above 17M file is probably below average size of what I see around here. I think more often I see 20M+ or 30M+ than I see less than that, except right after a fresh rotate. The dup actually begins about 2% into the log preceded by the ref. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata