update docs: "Mtime Only" may be ignored when using multiple option blocks in FileSet #1839
Description
Bareos component version
bareos-fd - 23.0.3~pre135.a9e3d95ca
bareos-dir - 23.0.3~pre135.a9e3d95ca
Steps to reproduce
FileSet has the Mime Only option set to yes:
FileSet {
Name = "fileset 1"
Include {
Options {
signature = SHA1
onefs = no
**mtime only = yes**
}
Options {
Exclude = yes
Regex = "some regex"
}
File = "/directory"
}
}
Expected results
Backup only files with mtime changed and not backup files with ctime changed.
Actual results
Bareos backups also files, where mtime is unchanged and only ctime is changed.
In the client log i can see mtime_only=0.
Environment
- bareos-dir OS: Ubuntu 22.04.4 LTS
- bareos-fd OS: Debian GNU/Linux 12 (bookworm)Relevant log output
Client log when running job estimate:
-----------------------------------------------------------------------
root@client:~# bareos-fd --foreground --debug-level 99
bareos-fd (10): lib/parse_conf.h:442-0 ConfigResourcesContainer: new configuration_resources_ 561e52e94bb0
client-fd (10): filed/socket_server.cc:122-0 filed: listening on port 9102
client-fd (10): filed/socket_server.cc:122-0 filed: listening on port 9102
client-fd (50): lib/bnet.cc:143-0 TLS server negotiation established.
client-fd (50): lib/cram_md5.cc:106-0 send: auth cram-md5 <686268492.1717502419@R_CLIENT::cleint-fd> ssl=2
client-fd (50): lib/cram_md5.cc:61-0 my_name: <R_CLIENT::client-fd> - challenge_name: <R_DIRECTOR::bareos-dir>
client-fd (99): lib/cram_md5.cc:232-0 sending resp to challenge: o4/W31+HT4oDHnFzhy/MKD
client-fd (5): filed/dir_cmd.cc:1433-0 set sd auth key
client-fd (5): filed/dir_cmd.cc:1436-0 set sd ssl_policy to 4
client-fd (10): filed/dir_cmd.cc:1271-0 LevelCmd: level = incremental mtime_only=0
client-fd (10): filed/dir_cmd.cc:1271-0 LevelCmd: level = since_utime 1717408987 mtime_only=0 prev_job=job1.2024-06-03_14.00.01_15
client-fd (50): findlib/find.cc:169-0 Verify=<V> Accurate=<Cmcs> BaseJob=<Jspug5> flags=<2013612536>
-----------------------------------------------------------------------Relevant traces output
No response
Anything else?
I'm experienced this issue also in all versions of bareos 22.x when i first used the mtime only option.
I found also this bug reported for bareos 19.2.7 on bugs.bareos.org: https://bugs.bareos.org/view.php?id=1249