Hi,
Theoretically we could work around this by deleting the file in your working
copy... and then write the new data. But this has one essential problem:
What if for whatever reason the delete occured but the write didn't? (Or
when it stops half way). Now we write a temporary file and then move it in
place. This file move operation either succeeds, or it fails (leaving both
files). In both cases we don't lose data, while in the delete then write
case we would.
This method of making sure that you don't lose your data is used by
thousands (if not millions) of other applications and should just work.
The technical details from that Microsoft developer, indicate that disabling
the Search indexer helps, but that it does not resolve the issue. Having
just an Explorer Window open on the directory can trigger the same issue!
(I think all TortoiseSVN users agree that closing all explorers before you
attempt to perform a subversion operation is not an option?)
I will add a note to this issue, but feel free to extend the issue yourself
:=)
Bert
From: Erik Funkenbusch [mailto:erik_at_funkenbusch.com]
Sent: vrijdag 5 februari 2010 17:47
To: 'Bert Huijben'
Cc: users_at_subversion.apache.org
Subject: RE: Action needed to get critical SVN related fix in Windows 7 SP1
Thanks Bert,
Since I see you are the one who reported this issue in the bug tracker and
to Technet, thanks for that.
Perhaps it would be a good idea to include some additional information in
the bug tracker regarding turning off search indexing and/or exclude the
folder from anti-virus scans to work around the problem.
It seems like the issue could be worked around. The problem occurs when
files are moved on top of other files. Couldn't Subversion simply delete
the files before it moves them to solve the issue? I know it would be
slightly slower to do this, so maybe that's a concern. However, if the
issue is not fixed in SP1 and no publicly available hotfix occurs,
subversion may have to work around this.
From: Bert Huijben [mailto:bert_at_qqmail.nl]
Sent: Friday, February 05, 2010 9:00 AM
To: 'Dave Purrington'; 'Erik Funkenbusch'
Cc: users_at_subversion.apache.org; Mark Phippard
Subject: RE: Action needed to get critical SVN related fix in Windows 7 SP1
Hi,
The best way to make Microsoft know that you care about this issue is to
file a support issue with them. (It is a confirmed issue, so the support
incident fee shouldn't be calculated for it).
Most likely corporate users can get a specific update for this issue when it
is available. (I don't know if that is already the case). For the Subversion
community it would be much better if we get it released in a service pack
(or automatic update.
Thanks for everybody who helps us get this issue resolved!
Bert
BTW:
http://tinyurl.com/w7corrupt
is a shortcut to this forum post. (I use this url as the central point for
information about this issue; it is also referenced in the Subversion
issue).
From: Dave Purrington [mailto:dave.purrington_at_gmail.com]
Sent: donderdag 4 februari 2010 23:34
To: Erik Funkenbusch
Cc: users_at_subversion.apache.org
Subject: Re: Action needed to get critical SVN related fix in Windows 7 SP1
Erik, what is the method for this kind of feedback? Is it enough to leave a
message on the note? Or are you asking that we call our rep? Should we file
a ticket about it?
On Thu, Feb 4, 2010 at 4:16 PM, Erik Funkenbusch <erik_at_funkenbusch.com>
wrote:
I forgot to include the Technet url
http://social.technet.microsoft.com/Forums/fi-FI/w7itprogeneral/thread/df935
a52-a0a9-4f67-ac82-bc39e0585148
Someone posted about what is essentially Subversion issue 3574
(http://subversion.tigris.org/issues/show_bug.cgi?id=3574) on the technet
forums and received a response from Neal Christensen, the NTFS Lead
Developer. He indicated that this is a known issue in Windows 7, but was
not scheduled for inclusion in SP1 because it was not receiving much
feedback.
If you have access to send Microsoft feedback on this issue, it is in
everyone's best interest if as many people do so as they can to get this
issue included in SP1. This seriously affects those using Windows 7 as both
a server and client for Subversion.
Received on 2010-02-05 18:04:53 CET