Background:
I use rsync to shuffles files around from my production server and
testing server. The testing server's central file share (the one
that the production server pulls from) is a smbmount from an internal
file server (OSX 10.4, but this is irrelevant as you'll see). I had
to switch from NFS to Samba after the 10.4 upgrade due to their new
NFS implementation breaking readdir(). After doing this, all my
rsync's from the test server (on the smbmount directory) to the
production server started listing nearly every file in any directory
I'd sync. Rsync builds its transfer list from file sizes and
*timestamps*.
What's happening:
On smbmount'd shares, files created during the winter have their time
stamp listed as one hour earlier as they are on the actual servers.
This is happening not only on the OSX 10.4 box to the production
server, but also if the *production server* does a local mount (eg:
"mount -t smbfs -U username //127.0.0.1/username /blah") of some
share, such as a home directory. Here's some sample output:
-- outputs from the production server connecting to 127.0.0.1 --
In the smbmount:
-rwxrwxr-x 1 root root 27613 Jan 20 08:16 2004 1040EZ.pdf*
-rwxrwxr-x 1 root root 11044 May 11 09:44 payfuse.tcpdump*
in the smbclient:
2004 1040EZ.pdf 27613 Thu Jan 20 09:16:54 2005
payfuse.tcpdump 11044 Wed May 11
09:44:42 2005
In my actual home dir:
-rw-rw-r-- 1 gabebug mis 27613 Jan 20 09:16 2004 1040EZ.pdf
-rw-rw-r-- 1 gabebug gabebug 11044 May 11 09:44 payfuse.tcpdump
-- and some examples from the example cited in "Background", the 10.4
server to the production server --
Locally, on the OSX Samba server:
-rw-rw-r-- + 1 rachelbu mudbug 2266 Mar 21 09:33 damon1.jpg
A separate random OSX client, over AFP:
-rwxr--r-- 1 gabebug gabebug 2266 Mar 21 09:33 damon1.jpg*
Production server, over `smbclient`:
damon1.jpg 2266 Mon Mar 21 09:33:23 2005
Production server, over `smbmount` (mount -t smbfs):
-rwxrwxr-x 1 root root 2266 Mar 21 08:33 damon1.jpg*
This behavior is obviously only occurring in smbmount, and smbclient
isn't affected. This also isn't a reaction between OSX and the
production server, as it occurs just the same locally.
The production client is running Linux kernel version 2.4.29 and
Samba 3.0.13. These are a minor version behind, but I saw nothing
mentioning timestamps/DST in either changelogs.
The /etc/localtime on all of my servers is set to /usr/share/zoneinfo/
US/Central
I'm unclear if this is a kernel VFS/SMBFS bug, a smbmount bug, or
some configuration flag I haven't run into, but either way the
inconsistency between smbmount and smbclient is concerning.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
