Linda W
2005-Jul-31 20:21 UTC
[Samba] BUG: Standard Time v. DST calculated wrong by Samba Server
FYI, the same bug apears if one mounts the file system using "cifs": -rwxr----- 1 user 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3* -rwxr----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3* Linda W wrote:> Summary: > There appears to be a bug in the "time range" Samba is using on > dates where time is scheduled to "Spring Forward" from Standard > to Daylight Savings time. Might want to review the code for > "Falling back", as well... > > Details: > > This started out with my thinking it was an rsync problem, but > it appears to be something to do with how samba is exporting the > file time (!? or Windows is reading 1 file). > > I have 2 files in a windows directory, /tmp/files: fo1.mp3, fo2.mp3. > I rsynced them to a directory on a linux box running SuSE 9.1 > with samba-3.0.9-2.6. > > On the linux/samba server, I see times: > target> ll --full-time > total 6264 > -rwxr----- 1 user 2532415 2000-04-02 01:34:50.000000000 -0800 fo1.mp3* > -rwxr----- 1 user 3876671 2000-03-12 22:33:20.000000000 -0800 fo2.mp3* > > (which are the same times as on the Windows source dir:) > /tmp/files> ll --full-time > total 6272 > -rw-r----- 1 user 2532415 2000-04-02 01:34:50.000000000 -0800 fo1.mp3 > -rw-r----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3 > > But, the Win XP's view of the remote files differs on 1 file: > /tmp/files> ll --full-time /k/target/ > total 7168 > -rw-r----- 1 user 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3 > ---------------------------------------^ > -rw-r----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3 > > This is 1 file out of 387 that has this problem. > > The same problem occurs when I use smbmount on the server to mount the > exported samba share (but mounted by root): > > -rwxr-xr-x 1 root 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3 > ---------------------------------------^ > -rwxr-xr-x 1 root 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3 > --------- > Note -- same time as seen on the Windows box, but this time it is seen > through the linux based "smbmount"ed view. > > It seems to be a bug related to the the time changing on that date > from Standard to Daylight Saving Time. To be more particular, on that > date, times in the range >=2:00AM and <3:00AM would not exist. It > would appear the code for time checking is using the wrong time range > on that date. > > Linda > >
Chad Vincent
2005-Aug-01 13:16 UTC
[Samba] Re: BUG: Standard Time v. DST calculated wrong by Samba Server
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On a related note, on one system we use a command line utility to do an incremental backup of certain files on the Samba server. It checks the timestamp on two files, and copies the newer over the older one. Every year, right after DST change (Both Spring and Fall,) the utility insists that every file has changed. While this normally doesn't cause problems, it is a hassle to wait for nearly a GB to transfer over the network. (Basically making a backup of a few critical files to the CEO's laptop, and Windows Briefcase kept having a corrupt DB.) I'm presuming the two bugs are related somehow.> 3. BUG: Standard Time v. DST calculated wrong by Samba Server > (Linda W) > ------------------------------------------------------------------------ > > Subject: > [Samba] BUG: Standard Time v. DST calculated wrong by Samba Server > From: > Linda W <samba@tlinx.org> > Date: > Sun, 31 Jul 2005 13:21:04 -0700 > To: > samba@lists.samba.org > > To: > samba@lists.samba.org > > Content-Transfer-Encoding: > 7bit > Precedence: > list > Message-ID: > <42ED32B0.1080201@tlinx.org> > Content-Type: > text/plain; charset=UTF-8; format=flowed > MIME-Version: > 1.0 > Message: > 3 > > > FYI, the same bug apears if one mounts the file system > using "cifs": > > -rwxr----- 1 user 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3* > -rwxr----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3* > > Linda W wrote: > >> Summary: >> There appears to be a bug in the "time range" Samba is using on >> dates where time is scheduled to "Spring Forward" from Standard >> to Daylight Savings time. Might want to review the code for >> "Falling back", as well... >> >> Details: >> >> This started out with my thinking it was an rsync problem, but >> it appears to be something to do with how samba is exporting the >> file time (!? or Windows is reading 1 file). >> >> I have 2 files in a windows directory, /tmp/files: fo1.mp3, fo2.mp3. >> I rsynced them to a directory on a linux box running SuSE 9.1 >> with samba-3.0.9-2.6. >> >> On the linux/samba server, I see times: >> target> ll --full-time >> total 6264 >> -rwxr----- 1 user 2532415 2000-04-02 01:34:50.000000000 -0800 fo1.mp3* >> -rwxr----- 1 user 3876671 2000-03-12 22:33:20.000000000 -0800 fo2.mp3* >> >> (which are the same times as on the Windows source dir:) >> /tmp/files> ll --full-time >> total 6272 >> -rw-r----- 1 user 2532415 2000-04-02 01:34:50.000000000 -0800 fo1.mp3 >> -rw-r----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3 >> >> But, the Win XP's view of the remote files differs on 1 file: >> /tmp/files> ll --full-time /k/target/ >> total 7168 >> -rw-r----- 1 user 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3 >> ---------------------------------------^ >> -rw-r----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3 >> >> This is 1 file out of 387 that has this problem. >> >> The same problem occurs when I use smbmount on the server to mount the >> exported samba share (but mounted by root): >> >> -rwxr-xr-x 1 root 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3 >> ---------------------------------------^ >> -rwxr-xr-x 1 root 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3 >> --------- >> Note -- same time as seen on the Windows box, but this time it is seen >> through the linux based "smbmount"ed view. >> >> It seems to be a bug related to the the time changing on that date >> from Standard to Daylight Saving Time. To be more particular, on that >> date, times in the range >=2:00AM and <3:00AM would not exist. It >> would appear the code for time checking is using the wrong time range >> on that date. >> >> Linda- -- Chad Vincent RhiannonWeb chad@rhiannonweb.com