[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion & FAT failures

From: Carl Karsten <carl_at_personnelware.com>
Date: 2005-06-26 20:13:43 CEST

Erik Huelsmann wrote:
> On 6/26/05, Carl Karsten <carl@personnelware.com> wrote:
>
>>Erik Huelsmann wrote:
>>
>>>After switching sussman's testsystem to FAT, it started failing lots of
>>>tests. From the logs, I conclude that status incorrectly reports files as
>>>unchanged. Checking manually with TSVN, I see the same. 'touch'-ing the file
>>>turns it into a 'changed' status.
>>>
>>>What we have here is the problem that FAT has a 2 second timestamp
>>>resolution, whereas we only 'sleep-for-timestamps' for 1 second.
>>>
>>>Conclusion: We're currently broken for use on FAT.
>>>
>
>
>
>>How does this effect use in the real world? My guess is the failure is due to the
>>automated test: update/sleep/check, which wouldn't happen in the real world.
>>

> Subversion uses a changed-detection heuristic based heavily on the
> timestamp of the file. To be able to detect changes made to files
> immediately after the client exits , it waits a second after some
> operation, hoping that enough time has passed so the changes lead to
> a new timestamp. On FAT this won't work, because the second is too
> short: it has a 2sec resolution.
>

That didn't answer my question. I am wondering what the chances are of this
issued impacting normal usage, where "normal" is a person doing everything
interactively, not a script that simulates things happing faster than is humanly
possible.

Carl K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 26 20:11:49 2005

This is an archived mail posted to the Subversion Dev mailing list.