I don't have mtimeonly set. I mv'd a sample file in my home directory as an experiment and saw that stat reports that atime, mtime remain unchanged but ctime does change as you expected.
When I stat one of the files I moved before, I see that ctime did not change. I had previously mv'd a whole subdirectory containing several subdirectories, each with a dozen or so files. I see that the mv'd subdirectory ctime changes but ctime for the contained subdirectories and files does not. This presumably is why they did not get backed up. I set the accurate flag in the job resource and then the files do get backed up. -Chris- On Mon, 12 Feb 2024, 20:33 Martin Simmons, <mar...@lispworks.com> wrote: > Do you have the mtimeonly option set in the FileSet? > > I would expect mv to change the ctime. Can you repeat this (mv not > changing > the ctime)? > > __Martin > > > >>>>> On Sun, 11 Feb 2024 09:17:10 +0000, Chris Wilkinson said: > > > > I'm seeing that files that are mv'd within the same folder are not being > > backed up by incr or diff backups. This is on Bacula v11, Debian 11. > > > > I'm guessing that this is because mtime and ctime are unchanged by mv and > > that the full path is not used. > > > > This is not a big problem I suppose because the files are still there in > > the last full and will get backed up in the next full. > > > > I'm just wondering if this is intended functionality or a > mis-configuration > > on my part? > > > > Chris Wilkinson > > >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
