What "just works!" on my side: 1. force uninstall btrfsmaintenance via rpm -e --nodeps <pkg> 2. lock btrfsmaintenance via zypper al btrfsmaintenance 3. zypper dup <your options> 4. reboot the system. 5. unlock btrfsmaintenance via zypper rl btrfsmaintenance 6. install btrfsmaintenance again via zypper in --no-r btrfsmaintenance Having btrfsmaintenance installed during zypper dup is more hassle than I'd like. As my only btrfs partition is only for docker containers, it's just not worth having it in any way active during zypper dup. Just my two cents, does anyone have better ideas? - Yamaban. On Thu, 21 Mar 2019 18:42, Christian Mahr <christian.mahr.ulm@...> wrote:
same experience on my side today. I actually re-installed btrfsmaintenance with "-f" option to be sure the version is consistently. And then did another "zypper dup" for the rest of the packages.
BR Christian
Am 21.03.19 um 18:37 schrieb Michael Pujos:
I just updated to this snapshot (usual 'zypper dup --no-allow-vendor-change' run in single user mode) and it resulted in installing btrfsmaintenance stalling on 'systemctl try-restart':
11210 root 20 0 255M 128M 29012 S 0.0 0.8 0:14.30 │ └─ zypper dup --no-allow-vendor-change 11756 root 20 0 27260 24344 5200 S 0.0 0.2 0:00.06 │ ├─ rpm --root / --dbpath /var/lib/rpm -U --percent --noglob --force --nodeps -- /var/cache/zypp/packages/openSUSE-20181213-0/noarch/btrfsmaintenance-0.4.2-2.1.noarch.rp11796 root 20 0 3916 2904 2600 S 0.0 0.0 0:00.00 │ │ └─ /bin/sh /var/tmp/rpm-tmp.qoPNmU 1 11834 root 20 0 3916 1872 1564 S 0.0 0.0 0:00.00 │ │ └─ /bin/sh /var/tmp/rpm-tmp.qoPNmU 1 11835 root 20 0 15640 10112 7796 S 0.0 0.1 0:00.04 │ │ └─ /usr/bin/systemctl try-restart btrfsmaintenance-refresh.service btrfsmaintenance-refresh.path btrfs-balance.service btrfs-balance.timer btrfs-defrag.service
I interrupted it with CTRL-C and tried to run it again, but rpm was locked thus I had to kill -9 the rpm process and sh scripts above. A new run of 'zypper dup' completed (although I saw briefly an error when it tried to install btrfsmaintenance) and after a reboot everything works, although I'm not entirely certain btrfsmaintenance updated correclty (but from the POV of the systen it is updated).
--