Kevin Keane wrote:
> Easy solution: use "touch" to fix the file date. Or wait 15 years and
> ten months and the problem will go away by itself.
Yes, I am in the process of doing the touch thing. But the fact that these
files get
backed up makes me thing something is a little bit wrong with the
On Wed, May 13, 2009 at 8:27 AM, John Drescher wrote:
> On Wed, May 13, 2009 at 3:40 AM, Graham Keeling wrote:
>> On Tue, May 12, 2009 at 09:54:25AM -0700, Mark Nienberg wrote:
>>> I have a bunch of files on a file server that have dates in the future like
>>> 3/28/2025. These are mostly image f
On Tue, May 12, 2009 at 09:54:25AM -0700, Mark Nienberg wrote:
> I have a bunch of files on a file server that have dates in the future like
> 3/28/2025. These are mostly image files downloaded from a digital camera
> that
> probably had the date set incorrectly.
>
> I noticed that these files
Easy solution: use "touch" to fix the file date. Or wait 15 years and
ten months and the problem will go away by itself.
Mark Nienberg wrote:
> I have a bunch of files on a file server that have dates in the future like
> 3/28/2025. These are mostly image files downloaded from a digital camera
: [Bacula-users] bad file dates cause incremental backups
I have a bunch of files on a file server that have dates in the future like
3/28/2025. These are mostly image files downloaded from a digital camera that
probably had the date set incorrectly.
I noticed that these files are included in
I have a bunch of files on a file server that have dates in the future like
3/28/2025. These are mostly image files downloaded from a digital camera that
probably had the date set incorrectly.
I noticed that these files are included in every incremental backup, even
though they
have not chang
