Here's a sample of the output I get from rdist -D for a file that it
thinks needs to be updated:


sendf(IMG_1615.JPG, 10<REMOVE>)
except(/home/rosalind/My Pictures/2007/GS - Winchester House/IMG_1615.JPG)
update(IMG_1615.JPG, 10<REMOVE>, 803ad40)
buf = QIMG_1615.JPG
update reply:  Y1072182 1179994768
updating: /home/rosalind/My Pictures/2007/GS - Winchester House/IMG_1615.JPG
buf = R20 666 1072182 1215095523 shannon staff IMG_1615.JPG

Here's the timestamps of the file after updating.  The first is the
source, the second is the destination:

-rw-rw-rw-   1 shannon  staff    1072182 May 24  2007 /home/rosalind/My 
Pictures/2007/GS - Winchester House/IMG_1615.JPG
                 timestamp: atime         Dec 12 13:16:36 2008
                 timestamp: ctime         Jul  3 07:32:03 2008
                 timestamp: mtime         May 24 01:19:28 2007

-rw-rw-rw-   1 shannon  staff    1072182 Jul  3 07:32 /home/pictures/2007/GS - 
Winchester House/IMG_1615.JPG
                 timestamp: atime         Dec 12 13:22:03 2008
                 timestamp: ctime         Dec 12 13:22:03 2008
                 timestamp: mtime         Jul  3 07:32:03 2008
                 timestamp: crtime        Dec 12 13:22:03 2008

The two long numbers in the rdist output correspond to the two
mtimes above.

I would've expected the mtime of the destination to match the mtime
of the source after the update, but it doesn't.

Comparing another file that *wasn't* updated:

-rw-rw-rw-   1 shannon  staff     994616 May 24  2007 /home/rosalind/My 
Pictures/2007/GS - Winchester House/IMG_1614.JPG
                 timestamp: atime         Dec 12 04:56:04 2008
                 timestamp: ctime         Jul  3 07:32:03 2008
                 timestamp: mtime         May 24 01:19:18 2007

-rw-rw-rw-   1 shannon  staff     994616 Jul  3 07:32 /home/pictures/2007/GS - 
Winchester House/IMG_1614.JPG
                 timestamp: atime         Dec 12 05:01:32 2008
                 timestamp: ctime         Dec 12 05:01:32 2008
                 timestamp: mtime         Jul  3 07:32:03 2008
                 timestamp: crtime        Dec 12 05:01:32 2008

The mtimes don't match there either.

If I run rdist again in verify (-v) mode, it does *not* say that the
above file needs to be updated.  It *does* say that the following file
needs to be updated:

-rw-rw-rw-   1 shannon  staff    1354035 May 24  2007 /home/rosalind/My 
Pictures/2007/GS - Winchester House/IMG_1620.JPG
                 timestamp: atime         Dec 12 00:34:38 2008
                 timestamp: ctime         Jul  3 07:32:03 2008
                 timestamp: mtime         May 24 01:50:26 2007

-rw-rw-rw-   1 shannon  staff    1354035 May 24  2007 /home/pictures/2007/GS - 
Winchester House/IMG_1620.JPG
                 timestamp: atime         Dec 12 00:40:06 2008
                 timestamp: ctime         Dec 11 05:01:54 2008
                 timestamp: mtime         May 24 01:50:26 2007
                 timestamp: crtime        Dec 11 05:01:54 2008

I sure can't see *why* that file needs to be updated; both size and
mtime match.

The good news is running rdist yet again in verify mode gives me the
same list of files to be updated, so at least the output is stable.
(But remember, since I had just run rdist to actually *do* the updating,
the output should be empty.)

Anyone have any idea what's going on here?
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss

Reply via email to