Re: [Samba] modification time inconsistency
[EMAIL PROTECTED] wrote: On Wed, Jul 11, 2007 at 12:14:19PM -0400, Chris Smith wrote: On Thursday 21 June 2007, Carlos Knowlton wrote: I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). Tried this out of curiosity and find the same results. It only happens with a zero length file, if the file has any data in it then the timestamp does change by doing a save in notepad (no data change necessary). With a zero length file it doesn't change when the file is on a Samba share. However with a cifs mounted Samba share a touch filename does update the timestamp even for zero length files. I've fixed this for 3.0.25c and later. Jeremy. Hello Jeremy, Any possibility this timestamp issue could be related to an issue I see when accessing Samba 3.0.23d (or 3.0.13 for that matter) from an OS X 10.4.x machine running Thursby's DAVE? There is a specific video editing application that runs on OS X. The application creates a pair of database files (two files) on every volume where audio and video media are store. One file is the actual database. One is a very small file that basically records when the last change was made to the database and how many files should be there. Every time you start the video application, the small file is touched (even if its contents are not modified). I reckon the application is marking when the last time was that it looked at this file. The problem is, the timestamp on the small file usually gets set to the workstation time and not to the server time, whereas the big file always gets set to the server time. If the two times are out of sync, the application can get into a vicious circle in which every time it boots, it sees that the mtime of the small file is earlier than the mtime of the big database file -- and the application thinks this means it has to remake the big database file. On the next start of the application, the same happens again. (This never happens on the Windows XP version of the application, by the way.) Having both server and workstation time exactly synchronized seems to aleviate the problem on OS X. However, it's difficult to enforce what users do to their workstations in terms of configuring NTP. Has something changed in Samba 3.0.25c that would cause the mtimes to always be server time? We don't see this issue with Apple's native SMB client, but then again the native client has some serious performance issues so that's why we don't use it. Regards, Andy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
On Fri, Jul 13, 2007 at 10:35:45AM -0400, AndyLiebman wrote: Any possibility this timestamp issue could be related to an issue I see when accessing Samba 3.0.23d (or 3.0.13 for that matter) from an OS X 10.4.x machine running Thursby's DAVE? Possible, but doesn't sound like what you describe. You could try checking out the SAMBA_3_0_25 branch (that'll be what's in 3.0.25c) and testing it. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
On Wed, Jul 11, 2007 at 12:14:19PM -0400, Chris Smith wrote: On Thursday 21 June 2007, Carlos Knowlton wrote: I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). Tried this out of curiosity and find the same results. It only happens with a zero length file, if the file has any data in it then the timestamp does change by doing a save in notepad (no data change necessary). With a zero length file it doesn't change when the file is on a Samba share. However with a cifs mounted Samba share a touch filename does update the timestamp even for zero length files. I've fixed this for 3.0.25c and later. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
On 7/12/07, Jeremy Allison [EMAIL PROTECTED] wrote: On Wed, Jul 11, 2007 at 12:14:19PM -0400, Chris Smith wrote: On Thursday 21 June 2007, Carlos Knowlton wrote: I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). Tried this out of curiosity and find the same results. It only happens with a zero length file, if the file has any data in it then the timestamp does change by doing a save in notepad (no data change necessary). With a zero length file it doesn't change when the file is on a Samba share. However with a cifs mounted Samba share a touch filename does update the timestamp even for zero length files. I've fixed this for 3.0.25c and later. Jeremy. This is wonderful, Thanks! Any idea when 3.0.25c will be released? Thanks! Carlos -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
On Thu, Jul 12, 2007 at 02:37:01PM -0500, Carlos Knowlton wrote: This is wonderful, Thanks! Any idea when 3.0.25c will be released? Week after next I think. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
Hey Guys, I have also noticed this problem; we have a ftp server with samba on it. I was trying to use find with mtime to remove folders older then 6 months. However when a folder is moved through a samba share the date stamp stays the same. This causes issues as old folders that want to be kept are moved; however the date stamp still remains the same. Is this going to be fixed in 3.2.0? Cheers, Adrian S. From: Carlos Knowlton [EMAIL PROTECTED] To: Jeremy Allison [EMAIL PROTECTED] CC: samba@lists.samba.org Subject: Re: [Samba] modification time inconsistency Date: Wed, 11 Jul 2007 09:45:11 -0500 On 6/21/07, Jeremy Allison [EMAIL PROTECTED] wrote: On Thu, Jun 21, 2007 at 03:50:51PM -0500, Carlos Knowlton wrote: Hello, I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). I know this seems pretty trivial, but it seems to make all the difference for some backup and SCADA software packages. Any ideas what I could do to fix this? Can you test against 3.0.25a (or soon b) to see if this is currently a problem please ? Thanks, Jeremy. Sorry for the delay in getting back to you on this. I have checked the latest Samba version, and the same behavior I saw in 3.0.22 also exists in 3.0.25b. Any ideas what might be happening, or how to fix this? Thanks, Carlos _ Movie session times on Messenger - add Movie Scout today! http://ninemsn.com.au/share/redir/adTrack.asp?mode=clickclientID=785referral=hotmailtagline0707URL=http://www.yourmovies.com.au/messenger/signup/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
On 6/21/07, Jeremy Allison [EMAIL PROTECTED] wrote: On Thu, Jun 21, 2007 at 03:50:51PM -0500, Carlos Knowlton wrote: Hello, I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). I know this seems pretty trivial, but it seems to make all the difference for some backup and SCADA software packages. Any ideas what I could do to fix this? Can you test against 3.0.25a (or soon b) to see if this is currently a problem please ? Thanks, Jeremy. Sorry for the delay in getting back to you on this. I have checked the latest Samba version, and the same behavior I saw in 3.0.22 also exists in 3.0.25b. Any ideas what might be happening, or how to fix this? Thanks, Carlos -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
On Thursday 21 June 2007, Carlos Knowlton wrote: I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). Tried this out of curiosity and find the same results. It only happens with a zero length file, if the file has any data in it then the timestamp does change by doing a save in notepad (no data change necessary). With a zero length file it doesn't change when the file is on a Samba share. However with a cifs mounted Samba share a touch filename does update the timestamp even for zero length files. Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
On Wed, Jul 11, 2007 at 09:45:11AM -0500, Carlos Knowlton wrote: On 6/21/07, Jeremy Allison [EMAIL PROTECTED] wrote: On Thu, Jun 21, 2007 at 03:50:51PM -0500, Carlos Knowlton wrote: Hello, I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). I know this seems pretty trivial, but it seems to make all the difference for some backup and SCADA software packages. Any ideas what I could do to fix this? Can you test against 3.0.25a (or soon b) to see if this is currently a problem please ? Thanks, Jeremy. Sorry for the delay in getting back to you on this. I have checked the latest Samba version, and the same behavior I saw in 3.0.22 also exists in 3.0.25b. Any ideas what might be happening, or how to fix this? Can you log a bug in bugzilla please so I can track it ? Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
On 7/11/07, Jeremy Allison [EMAIL PROTECTED] wrote: On Wed, Jul 11, 2007 at 09:45:11AM -0500, Carlos Knowlton wrote: On 6/21/07, Jeremy Allison [EMAIL PROTECTED] wrote: On Thu, Jun 21, 2007 at 03:50:51PM -0500, Carlos Knowlton wrote: Hello, I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). I know this seems pretty trivial, but it seems to make all the difference for some backup and SCADA software packages. Any ideas what I could do to fix this? Can you test against 3.0.25a (or soon b) to see if this is currently a problem please ? Thanks, Jeremy. Sorry for the delay in getting back to you on this. I have checked the latest Samba version, and the same behavior I saw in 3.0.22 also exists in 3.0.25b. Any ideas what might be happening, or how to fix this? Can you log a bug in bugzilla please so I can track it ? Thanks, Jeremy. Okay, I've reported this issue in Bugzilla under ID 4779https://bugzilla.samba.org/show_bug.cgi?id=4779 Thanks! -Carlos -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] modification time inconsistency
On Thu, Jun 21, 2007 at 03:50:51PM -0500, Carlos Knowlton wrote: Hello, I have a client with a windows utility that relies on touching (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the file. (ie, clicking save in notepad doesn't change the mod time unless he enters some data first.). I know this seems pretty trivial, but it seems to make all the difference for some backup and SCADA software packages. Any ideas what I could do to fix this? Can you test against 3.0.25a (or soon b) to see if this is currently a problem please ? Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
