David Epping

Thanks so much! Yes, it works correctly in my setup as well.

I hope this is a supported use case after all. It seems like the exclude-other-filesytems parameter is not in duply.sh and it must have been added to the config many years ago ...

Hi ede, thanks for putting in all that effort. While stripping down the config to something minimal that still shows the issue, I found that I can toggle between working and not working by commenting or having active my exclude-other-filesystems line. I also found that only the MAX_FULLBKP_AGE content xor the VOLSIZE content shows up in the commandline. If both are active VOLSIZE does not show up. This is the config showing the error and below outputs: BACKUP_BASE_DIR='/srv/duply' DUPL_PARAMS="$DUPL_PARAMS...

My initial config had only MAX_FULLBKP_AGE uncommented and this was what triggered the problem for me. When creating the bug report, because it looked similar, I also tried with VOLSIZE briefly and saw it fail. I just re-tested and the error message is as follows, with default VOLSIZE of 50: 2025-08-26T22:05:50.147354+02:00 share duply-backup: --- Start running command PURGE at 2025-08-26 22:05:50.140 --- 2025-08-26T22:05:50.246601+02:00 share duply-backup: CommandLineError: Wrong number of positional...

Hi ede, thanks a lot. Just let me know if you need additional information from my side. Best regards, David

Incomatibility of MAX_FULLBKP_AGE with duplicity 3.0.4