C.A.T.Magic wrote:
>
> Hi
>
> I just read your 1.1 release proposal and now try to hurry
> to inform you that there are -still- several severe issues
> with the new fsfs when doing multiple commits at the same time
> on win32 svn, version 1.0.4 (r9844) windows xp sp1/latest patches.
>
> the problem is the same as discussed a while ago:
> use 1 repos, 2 or more working dirs,
> simultaneously loop over a modify-commit
> from both working dirs resulting in weird errors like
> the following:
>
>
> Sending Version2.h
> Transmitting file data .svn: Commit failed (details follow):
> svn: Invalid diff stream: insn 2 has non-positive length
>
>
> Sending Version2.h
> svn: Commit failed (details follow):
> svn: Reference to non-existent node '0.0.t9-1' in filesystem
> 'X:/SVNSandbox/Test
> FS/Repos/db'
>
>
> ============== (again tried with another repos)
>
> Sending Version.h
> Transmitting file data .svn: Commit failed (details follow):
> svn: Checksum mismatch for resulting fulltext
> (Version.h):
> expected checksum: 8ddd214ec052d5ee4c652996e1c0a123
> actual checksum: 00997804605b81104cc9a1b18c783031
>
>
> Sending Version.h
> Transmitting file data .svn: Commit failed (details follow):
> svn: Can't remove 'x:/svnsandbox/testfs/repos/db/transactions/92-1.txn':
> The directory is not empty.
>
>
> Sending Version.h
> Transmitting file data .svn: Commit failed (details follow):
> svn: Can't remove 'x:/svnsandbox/testfs/repos/db/transactions/92-1.txn':
> The directory is not empty.
> Sending Version.h
> svn: Commit failed (details follow):
> svn: Out of date: 'Version.h' in transaction '93-1.txn-2'
>
>
> Sending Version2.h
> svn: Commit failed (details follow):
> svn: Found malformed header in revision file
>
>
> ==================================
>
>
> so all this doesnt sound very good.
> especially after the last message happens, the repository is unusable.
Note that this is /not/ win32 specific. I was able to reproduce on
FreeBSD with stress.pl. I haven't seen the 'malformed header' stuff
yet, but I did get the checksum mismatch part, so something is wrong.
> also the recovery procedure doesn't really work:
>
>
> svnadmin verify reports:
> * Verified revision 27.
> svn: Found malformed header in revision file
>
> svnadmin recover reports:
> Recovery completed.
> The latest repos revision is 93.
Well, "not work" isn't really the right word for it. svnadmin recover
doesn't really do anything at all for an fsfs repository. In theory it
isn't needed. Of course theory and practice appear to be slightly
different in this case...
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 9 02:32:38 2004