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

RE: FAT32 svn errors

From: D.J. Heap <djheap_at_dhiprovo.com>
Date: 2003-04-15 21:50:14 CEST

Hmm, yes, that is possible, but I usually disable that service on my
development machines (total waste of cpu/memory/disk IMO). It *is*
turned off now, but I will turn it back on and run for a few days to see
if I start getting failures again.

DJ

-----Original Message-----
From: mark benedetto king [mailto:mbk@boredom.org]
Sent: Tuesday, April 15, 2003 1:28 PM
To: D.J. Heap
Cc: Subversion Dev List
Subject: Re: FAT32 svn errors

On Tue, Apr 15, 2003 at 09:09:38AM -0600, D.J. Heap wrote:
> It seemed to me like there was some fishy behavior in MoveFileEx, but
I
> could never prove it in a test setup.
>

I wish I could remember who thought of this so that I could credit
them appropriately, but someone suggested that perhaps the Indexing
Service,
or some other such filesystem-crawling-thing was running, holding a
lock,
and preventing the move.

This would explain

  1.) the difficulty reproducing the problem
  2.) the fact that a multi-processor configuration seemed to
      trigger the problem.

--ben

**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email
in error please notify the system manager.

This footnote also confirms that this email message has been
swept by MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 15 21:51:08 2003

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

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