Opened 13 years ago

Closed 11 years ago

#165 closed defect (fixed)

Timestamp not updated after copying to the OS/2 share

Reported by: dmik Owned by: Silvan Scherrer
Priority: major Milestone: Samba Server for eCS (OS/2) 1.1.x
Component: Samba Server Version: Server 3.3.x
Keywords: Cc:

Description

If you copy a bunch of files to the OS/2 share, some files will have their original dates, some files will get the current date.

To me, it looks like the time stamp is not always updated correctly on the server after the copy operation is completed.

Steps to reproduce:

  1. Connect to an OS/2 share.
  2. Copy a bunch of files from your local machine to it.
  3. Compare the file timestamps with the originals.

Change History (13)

comment:1 Changed 13 years ago by dmik

I have use two clients for accessing CIFS/SMB shares in my environment (Linux, MacOS): the regular Samba client and the proprietary Sharity client (which gives much better performance close to the real throughput of the network). The results a bit differ:

  1. When using the Samba client (from Linux or from OS/2), the dates are always wrong (current time).
  2. When using the Sharity client (from Linux), the dates are sometimes OK (50/50).

comment:2 Changed 13 years ago by dmik

Note that this happens with Samba 3.0.37-eCS 1.0.5-472 as well.

comment:3 Changed 12 years ago by dmik

This issue is still there. Tried the latest Samba 3.3 (1.1.2-3.3.1.6) and my fixed libc064.

comment:4 Changed 11 years ago by Neil Waldhauer

Is this still a "Minor" issue? Why is it so hard to fix? Can SAMBA provide a work-around?

comment:5 Changed 11 years ago by Silvan Scherrer

Component: Unknown → Samba Server
Owner: changed from nobody to Silvan Scherrer
Priority: minor → major

i higher the priority, so we will work on that hopefully soon.

comment:6 Changed 11 years ago by Silvan Scherrer

Milestone: → Samba Server for eCS (OS/2) 1.2.x

@BlondeGuy? Neil if you have a easy to reproduce scenario let us know. this would make it a lot easier.

comment:7 Changed 11 years ago by Neil Waldhauer

This happens every time for me. Both machines run eComStation. One has the latest SAMBA client and one has the latest server.

Copying one file to the server will show the bug. Timestamp will be original on the client, but will be the time of the copy on the server.

comment:8 Changed 11 years ago by Silvan Scherrer

Milestone: Samba Server for eCS (OS/2) 1.2.x → Samba Server for eCS (OS/2) 1.1.x

according to Yuri it happens also with a XP client. So it's for sure a server bug.

comment:9 Changed 11 years ago by Silvan Scherrer

see also #147 there it states it works for 3.0.x

comment:10 Changed 11 years ago by Silvan Scherrer

we added a possible fix for that in r790 r791 and r792 a new testversion should be available soon.

comment:11 Changed 11 years ago by Herwig Bauernfeind

​ftp://ftp.netlabs.org/pub/samba/server/test/test-ticket-165.zip

This is a Samba 3.3.16 smbd.exe with a possible fix.

comment:12 Changed 11 years ago by Neil Waldhauer

I installed the possible fix for SAMBA 3.3.16 smbd.exe, and copied the file as outlined above. The fix appears to work here. The timestamp is the same on client and server.

comment:13 Changed 11 years ago by Silvan Scherrer

Resolution: → fixed
Status: new → closed
Note: See TracTickets for help on using tickets.