Skip to content

Die KW 39/2020 im Link-Rückblick

zfs-snap-manager and "Got invalid schema for dataset" or not deleted old snapshots or not created new snapshots

I am using the zfs-snap-manager for such a long time that I never ever had a look on it since years.

I've just created zfs pools and zfs snap manager configurations without thinking or checking it for a while now. But once upon a time I wanted to check the behaviour and found out that some configured snapshots where not made.

After a while I saw that my assumption was false, so the error was in front of the display :-).

My configuration for the section schema was simplified to 7d because all I wanted for a dataset was that I can go back the last seven days. After finding the log file (/var/log/zfs-snap-manager.log) and tailing it, I quickly saw the log message Got invalid schema for dataset .... Just a bit more investigation and I found out that I have to provide a fully defined schema like 7d0w0m0y. After adapting all available configuration files on all hosts, the zfs-snap-manager is working as expected.

I found an existing feature request to "relaxed" the schema interpretion and stumpled over another feature request asking for creating unittests. So I've forked it and will try to learn python by fixing the issue on my own.

  • migrate code to python3
  • write unittests
  • implement relaxed handling of schema with default values

Do you want to join? Contact me if you want to.

Translate to de es fr it pt ja

Nextcloud Client 3.0.1 on Linx >> there are unresolved conflicts<<

As written in the official issue ticket, following the way how to solve your conflict locally.

A quick update to figure out the conflicted files. cd into your nextcloud synchronized path

#list conflicted files 
find . -iname *conflic* -type f

You can than decide which file is the one you want to keep or foo (conflicted copy 2020-09-09 083407).bar.

See also here and here.

Translate to de es fr it pt ja

Die KW 38/2020 im Link-Rückblick