Re: [rdiff-backup-users] Daylight Saving Time problem?

[Randall Nortman]

On Mon, Apr 04, 2005 at 05:29:35PM -0700, Ben Escoto wrote:
> >>>>> Randall Nortman <address@hidden>
> >>>>> wrote the following on Mon, 4 Apr 2005 09:19:49 -0400
> 
> Hi, the relevant files would be the current_mirror.<time> and the
> mirror_metadata.<time> ones.  One of them (probably the "earlier" one
> which is "2005-04-03T03:00:04-04:00") has no mirror_metadata.  So you
> can delete that one.

I have:

current_mirror.2005-04-03T01:45:03-05:00.data
current_mirror.2005-04-03T03:00:04-04:00.data

and:

mirror_metadata.2005-04-03T01:30:08-05:00.snapshot.gz
mirror_metadata.2005-04-03T01:15:04-05:00.snapshot.gz
mirror_metadata.2005-04-03T01:00:08-05:00.snapshot.gz
mirror_metadata.2005-04-03T00:45:03-05:00.snapshot.gz
[... lots more, but the above are the most recent ...]

So, *neither* of the current_mirror files has an associated
mirror_metadata file. Uh oh?

> The times shed some light on what the bug is.  The two times:
> 
> 2005-04-03T01:45:03-05:00
> 2005-04-03T03:00:04-04:00
> 
> are 45 minutes apart, not 15 minutes.  Do you know what the correct
> values should be for your timezone and when you ran it?

No offense, but check your math:

2005-04-03 01:45:03-05:00 = 2005-04-03 06:45:03 UTC
2005-04-03 03:00:04-04:00 = 2005-04-03 07:00:04 UTC

So, those are 15 minutes, 1 second apart, and they are at exactly the
times when the backup were supposed to run (plus or minus a few
seconds).  It should have run 15 minutes before DST took effect at
01:45, then DST takes effect at 02:00, so the clock jumps forward an
hour from 01:59:59 straight to 03:00:00 (never actually reads 02:00).

The timezone on both machines is US/Eastern, and the clocks are kept
accurate via ntpd.  There is some chance that since ntpd was running,
the clock on one of the machines was adjusted while rdiff-backup was
running.

Randall