http://bugzilla.opensuse.org/show_bug.cgi?id=1073204 Bug ID: 1073204 Summary: btrfsmaintenance: Ineffective switch to systemd timers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: antoine.belvire@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- With snapshot 20171214, btrfsmaintenance has ineffectively switched to systemd timers. Problems: - Upon update from the old package to the new package, systemd timers are not present when doing a 'systemctl list-timers --all'. So no btrfs maintenance operation will be performed. - Upon re-installation of the new package: * systemd timers are present but with n/a for all values * After reboot, timers are set, but with default periods which do not correspond to the configuration in /etc/sysconfig/btrfsmaintenance - For both cases, one has to call '/usr/share/btrfsmaintenance/btrfsmaintenance-refresh-cron.sh systemd-timer' to properly set the timers according to the configuration. - The btrfsmaintenance-refresh.service, which was already pretty useless as it cannot be started by the try-restart in %service_add_post, as it's a oneshot service, is worse now because it can only refresh cron symlinks. And as there is no protection in the refresh script to mutually exclude cron tasks and systemd timers, this may lead to have cron AND systemd timers activated for the same tasks. - I don't see the point to keep the possibility to use cron tasks knowing that any update of the package will (try to) replace them by systemd timers. You'd better just remove the possibility to have cron tasks and remove the useless btrfsmaintenance-refresh.service, it would be simpler. -- You are receiving this mail because: You are on the CC list for the bug.