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

Re: Update fails but fresh checkout works

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Tue, 2 Feb 2010 10:53:44 +0000

On 2 February 2010 10:34, Robin Guest <robin.guest_at_gmail.com> wrote:
> On 2 February 2010 10:05, Simon Large <simon.tortoisesvn_at_googlemail.com>
> wrote:
>>
>> On 2 February 2010 09:40, Robin Guest <robin.guest_at_gmail.com> wrote:
>> > On 2 February 2010 09:30, Simon Large <simon.tortoisesvn_at_googlemail.com>
>> > wrote:
>> >>
>> >> Is that permission denied in the local file system, or a permission
>> >> denied response from the SVN server?
>> >
>> > Ditto. After upgrading to win7 32-bit I got many intermittent permission
>> > denied errors on temp files in the local file system when updating dirs
>> > with
>> > externals, but never when doing fresh checkouts of those dirs. They all
>> > went
>> > away after I excluding my working copies from anti virus (Sophos) and
>> > windows indexing.
>>
>> I put this item in the FAQ a week or so ago. Are you able to tell
>> whether it was the indexing service or Sophos giving permission denied
>> errors? The error reported with indexing was different, although that
>> doesn't mean it is the only possible error.
>>
>> http://tortoisesvn.tigris.org/faq.html#cantmove2
>
> I would have said 99% certain it was Sophos - except I've just removed the
> exclusion and I now can't reproduce it. I'll leave it like that for a few
> days to see if I can capture any more info for you.
> Perhaps it was the combination of Sophos and indexing? Don't seem to be able
> to test that either, though - I apparently have AppData excluded 3 times(!),
> and the indexing UI only allows me to remove one of those.
> Sophos was also responsible for another more serious error. I run svnsync
> whenever my vpn connects, to sync the company repo to a local mirror. Very
> occasionally, Sophos would interfere with that so that synsync complained
> the mirror repo was damaged, then on the next reboot chkdsk would run and
> fix errors. Excluding the mirror repo in Sophos has stopped this happening
> since. I'm reluctant to remove the exclusion for that one again to provide
> you the exact error message, as it's such a pain to recreate and resync the
> mirror repo from scratch.

OK, thanks for looking. If it's not easy to test then don't bother.
And definitely don't put your data at risk.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2444105
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-02 11:53:53 CET

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.