On Mon, 05 Dec 2022 00:41:00 -0000, "Joe Salmeri" <jmscdba@gmail.com> wrote:
Not sure what you mean by "this is not the same".
The issue in [1] is not the same as yours because they had a broken filesystem, but their problem did involve 'snapper cleanup number' with the same generic error message you got.
Whether the service runs that command or I run it from the cmdline they produce the same results the only difference are those 2 journal messages which only come out when the service runs.
The "DadPC.fios-router.home" in the journal is not referring to your home partition, right?
[... (no apparent filesystem problems)]
Looking at /var/log/snapper.log ( thanks for that pointer ) I see:
[...] 2022-12-04 19:11:11 WAR libsnapper(17833) FileUtils.cc(SDir):91 - THROW: open failed path:/home/.snapshots/1 errno:2 (No such file or directory) 2022-12-04 19:11:11 WAR libsnapper(17833) Btrfs.cc(checkSnapshot):482 - CAUGHT: open failed path:/home/.snapshots/1 errno:2 (No such file or directory) 2022-12-04 19:11:41 MIL libsnapper(17833) Snapper.cc(~Snapper):142 - Snapper destructor 2022-12-04 19:12:11 MIL libsnapper(17833) snapperd.cc(main):315 - Exiting
[...] 2022-12-04 19:13:03 WAR libsnapper(17950) FileUtils.cc(SDir):91 - THROW: open failed path:/home/.snapshots/1 errno:2 (No such file or directory) 2022-12-04 19:13:03 WAR libsnapper(17950) Btrfs.cc(checkSnapshot):482 - CAUGHT: open failed path:/home/.snapshots/1 errno:2 (No such file or directory) 2022-12-04 19:13:03 WAR libsnapper(17950) FileUtils.cc(SDir):91 - THROW: open failed path:/home/.snapshots/1 errno:2 (No such file or directory) 2022-12-04 19:13:03 WAR libsnapper(17950) Btrfs.cc(checkSnapshot):482 - CAUGHT: open failed path:/home/.snapshots/1 errno:2 (No such file or directory) 2022-12-04 19:13:03 WAR libsnapper(17950) FileUtils.cc(SDir):91 - THROW: open failed path:/home/.snapshots/1 errno:2 (No such file or directory) 2022-12-04 19:13:03 WAR libsnapper(17950) Btrfs.cc(checkSnapshot):482 - CAUGHT: open failed path:/home/.snapshots/1 errno:2 (No such file or directory)
[...] 2022-12-04 19:13:17 ERR libsnapper(17950) Client.cc(dispatch):1951 - caught unknown exception 2022-12-04 19:13:17 WAR libsnapper(17949) errors.cc(convert_exception):39 - CAUGHT: dbus error exception 2022-12-04 19:13:17 WAR libsnapper(17949) errors.cc(convert_exception):52 - RETHROW: dbus error exception 2022-12-04 19:13:33 MIL libsnapper(17950) Snapper.cc(~Snapper):142 - Snapper destructor
The home snapshot ( /home/.snapshots/1 ) it refers too has not existed for close to 2 years since my home snapper config does timeline snapshots but only keeps the last 10 hours and the last 5 days.
I have little experience with snapper, and it has been a long time since I read the docs, but isn't snapshot #1 special in some way?
Not sure if those errors then cause the dbus error exception messages but clearly something in the cleanup process is broken if it is looking for something that hasn't existed in 2 years.
Running the following ( from the github link you provided )
snapper -v -c home cleanup timeline
Produces no output or errors but if I watch /var/log/snapper.log it gets the following
2022-12-04 19:32:15 WAR libsnapper(18407) FileUtils.cc(SDir):91 - THROW: open failed path:/home/.snapshots/1 errno:2 (No such file or directory) 2022-12-04 19:32:15 WAR libsnapper(18407) Btrfs.cc(checkSnapshot):482 - CAUGHT: open failed path:/home/.snapshots/1 errno:2 (No such file or directory)
Your output from '/usr/lib/snapper/systemd-helper --cleanup' showed that "Failure (error.something)" happened during "number cleanup for 'root'". Instead of 'snapper -v -c home cleanup timeline', how about trying 'snapper -v -c root cleanup number' ?
When you consider that there are no filesystem errors being reported by btrfs ( nor anything else ) and also that the timeline snapshots for the home config are being cleaned up properly it would seem that other than the attempt to access home snapshot #1 which has not existed for 2 years that it is working properly.
Any other thoughts? Thanks!
Run strace like they did in [1] to find what leads to the "Failure (error.something)." [1] https://github.com/openSUSE/snapper/issues/686 -- Robert Webb