http://bugzilla.opensuse.org/show_bug.cgi?id=1187392 http://bugzilla.opensuse.org/show_bug.cgi?id=1187392#c7 --- Comment #7 from Bernhard Wiedemann <bwiedemann@suse.com> --- May 20 21:29:00 mirrordb1 systemd-fsck[348]: ROOT: recovering journal May 20 21:29:00 mirrordb1 kernel: random: fast init done May 20 21:29:00 mirrordb1 systemd-fsck[348]: ROOT: Clearing orphaned inode 125827 (uid=0, gid=0, mode=0100644, size=10406312) May 20 21:29:00 mirrordb1 systemd-fsck[348]: ROOT: Clearing orphaned inode 128894 (uid=0, gid=498, mode=0100640, size=8388608) May 20 21:29:13 mirrordb1 kernel: XFS (vdb): Ending recovery (logdev: internal) May 21 00:00:08 mirrordb1 systemd[1]: Starting Rotate log files... May 21 00:00:14 mirrordb1 systemd[1]: Finished Rotate log files. The "orphaned inode" messages for vda1 (root partition) indicate that there might have been an earlier unclean shutdown (e.g. there was the power outage 20201118), so maybe postgresql data on vdb (xfs) was not as consistent as they should be. The logrotate could have triggered a service reload, but OTOH, I dont see any postgres-related files in /etc/logrotate.d/ -- You are receiving this mail because: You are on the CC list for the bug.