Release: 2.1.0.106 (Canary) 2025-01-11

Releases
1

2.1.0.106_canary_2025-01-11

This release is a canary release intended to be used for testing.

Note that this build has a redesigned restore flow
Should issues arise, the previous restore engine can be enabled with --restore-legacy=true.

Detailed list of changes:

  • Added server status and wait to ServerUtil
  • Fixed an issue where index files would contain replicated blocklists
  • Fixed an issue with duplicate blocks preventing repair
  • Size strings are now formatted as kikibytes
  • Fixed some issues with CIFS/SMB backend
2

Funny typo, but it’s good to use SI units for consistency.

3

It is actually not a typo, but I agree it is a non-intuitive name:

4

Yeah, kiki vs kibi… I like kibibytes due to binary options being preferred.

But, to the actual point why I’m here. I found still something, doesn’t really matter but is just minor annoyance. Now I did dig the info from logs.

2025-01-14 11.07.02 +02 - [Warning-Duplicati.Library.Main.Operation.Restore.FileProcessor-CreateMissingFolder]: Creating missing folder “d:\path” for file “d:\path\configuration.ini”
Version: - 2.1.0.106_canary_2025-01-11

Still seems to be there. → If I start restore, create that directory quickly and then it exists with Code: 0, but if I don’t manually create that directory, it exists with 2. Now I got the exact warning from log, so it should be possible to locate it.

Otherwise everything is now pretty great.

5

is still open. Because I got confused by the plan, I asked a question. You can review it as well.

6

I updated all my machines to .106 and so far so good. The new CIFS/SMB connector is now working well on my Linux machines and I’ve been able to remove the SMB mounts I was using before.

7

After upgrading for 2.1.0.104 (beta) I see the message that --use-block-cache is not supported. Is it OK? I think it was very useful parameter.

8

It hasn’t done anything since removal six years ago. This is just now causing notification.