Josip Deanovic wrote on 03/28/2017 09:10 PM:
> I believe that this could be a problem.
> It could be that bacula saved files with ctime during the last full
> backup and now sees all the files as changed even with the "mtimeonly"
> set to "yes".
>
> If this is the case it would be a good idea to change that behavior
> (unless there is a good reason not to).


Thanks, so are you saying this is potentially a bug with bacula?  Do you 
know how i could continue with incremental backups in the mean time? 
This particular fileset is 4 levels deep yet it contains over 21 million 
files and about 4 terabytes of gzip-compressed data.  Soon I will set up 
a new storage daemon with compressing filesystem so won't have to worry 
about gzip on the client side... but this particular full backup takes 
about 10 days to complete... would like to avoid it if possible.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users