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

Re: The REPORT request returned invalid XML in the response: XML parse

From: David James <james82_at_gmail.com>
Date: 2005-09-26 17:41:55 CEST

On 9/26/05, Jeff Squyres <jsquyres@open-mpi.org> wrote:
> 1 [lo-03-02]~/software/openmpi|> svn co
> http://svn.open-mpi.org/svn/ompi/trunk ompi-trunk
> svn: REPORT request failed on '/svn/ompi/!svn/bc/7442/trunk'
> svn: The REPORT request returned invalid XML in the response: XML parse
> error at line 1: mismatched tag (/svn/ompi/!svn/bc/7442/trunk)
> The problem is fairly repeatable -- a fresh "co" will work after 2-3
> tries, but trying to "up" after a successful checkout will nearly
> always result in the problem. He said that a second or third attempt
> to update would usually work properly. This is an anonymous /
> read-only checkout (note the http:). I have https write access to this
> repository and have not seen any problems like this at all, but the
> user was getting them fairly consistently earlier last week.
> Environments:
> Server:
> - Solaris 8
> - Apache 2.0.53
> - Subversion 1.1.4 (r13838)
> Client:
> - SVN 1.2.0
> - Debian stable, 64 bit (kernel -- some vendor extensions)
> There is one odd thing about the user's environment -- it's on a Lustre
> filesystem. The user does not seem to have this problem on an NFS
> filesystem. Are there any known issues with checking out/updating on
> Lustre filesystems?

Perhaps this fix by Hans Reiser will help? Hans wrote a patch to
truncates all new files to length zero, to help prevent corruption on
buggy filesystems. (His fix is intended for systems which use unfsd,
but it's possible that Lustre suffers from the same problems.)



David James -- http://www.cs.toronto.edu/~james
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 26 17:42:59 2005

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.