https://bugzilla.suse.com/show_bug.cgi?id=1165780 https://bugzilla.suse.com/show_bug.cgi?id=1165780#c61 --- Comment #61 from Fabian Vogt <fvogt@suse.com> --- (In reply to Franck Bui from comment #59)
(In reply to Goldwyn Rodrigues from comment #55)
How about enabling and starting the timer service only if /etc/systemd/system/$SERVICE.timer.d/schedule.conf does not match the $PERIOD in /etc/sysconfig/btrfsmaintenance? Would that solve the issue?
I think we already discussed about what is actually needed:
1. btrfsmaintenance-refresh.service should not be enabled by default by the preset stuff but instead it should enable btrfsmaintenance-refresh.path On Factory this was dealt by sr#829721
2. since btrfsmaintenance-refresh.service is not supposed to be run at boot the unit file should have an [Install] section. Not sure if this was fixed...
It was part of https://build.opensuse.org/request/show/831373.
IIRC this was based on the fact that btrfsmaintenance-refresh.service needs to be started only when settings were changed in /etc/sysconfig/btrfsmaintenance.
But please note that this addresses new installations only.
For existing systems, the relevant symlink have to be changed manually because the presets stuff are only apply at installation time.
Change 2 is enough and also affects existing installations properly, see comment 48.
Ideally after an update we should have renamed /etc/systemd/system/multi-user.target.wants/btrfsmaintenance-refresh.service to point to btrfsmaintenance-refresh.path instead.
AFAICS none of these changes has not been backported to *SLE*.
Backporting only sr#829721 should be sufficient. -- You are receiving this mail because: You are on the CC list for the bug.