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

Win7 NTFS corruption via TortoiseSVN

From: Colin Jensen <cjensen_at_abekas.com>
Date: Mon, 12 Oct 2009 15:22:24 -0700

On two different systems, I am running Windows 7 with TortoiseSVN
1.6.5 Build 16974 - 32 Bit. I also have Microsoft's "Security
Essentials" antivirus software running.

Some of this issue was already reported by Khash Sajadi. See
<http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2401470
>

On both machines I have attempted to perform a directory rename in a
checked out copy. I clicked on a directory named "foobar", selected
"rename" and entered "../foobar" or somesuch where the parent
directory .. is a valid, up to date part of the same working copy. On
both machines I received the
'blahblah\.​svn\entries': The file or directory is corrupted and
unreadable.
message that Khash reported.

On every machine this happens on, a chkdsk is performed by Windows
during the next reboot.

Half an hour ago, I had the same issue arise when performing a switch
operation on a working copy to switch from current to a branch. It
failed and immediately rebooting earned me an automatic checkdisk. I
tried to repeat the issue with a different working copy but never saw
the issue again.

I know NTFS corruption cannot be the fault of TortoiseSVN -- it's an
OS issue. I apologize for not having repeatable instructions. Might
I suggest that users should watch for this issue and let us all know
whether it is happening to them or not? Be sure to reboot and see if
the auto-chkdsk kicks in before reporting.

Cheers,

- Colin Jensen

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2406825

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-13 23:14:39 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.