Hi Philip. Usually to reproduce a bug we only need to look as far as the first time something goes wrong. I assume you have a specific reason in this case for thinking that the information about whether a *second* sync also fails will be helpful to you, but that may not have been clear to Kenneth.
- Julian ----- Original Message ----- > From: Philip Martin <philip.mar...@wandisco.com> > To: Kenneth Miles <kmi...@voyagergaming.com> > Cc: Stefan Sperling <s...@elego.de>; dev@subversion.apache.org > Sent: Tuesday, 22 May 2012, 11:08 > Subject: Re: ISSUE: "To many open files" not being logged by master server > when sync fails. > > Kenneth Miles <kmi...@voyagergaming.com> writes: > >> On 21/05/12 20:41, Philip Martin wrote: >>>> >>> You didn't answer the question about a second run. After >>> >>> svnadmin create ... >>> svnsync init ... >>> svnsync sync ... >>> >>> does another >>> >>> svnsync sync ... >>> >>> fail? >>> >>> I still can't reproduce it. Can you come up with a complete > recipe? >>> Which version of Subversion are you using? >>> >>> Are there other changes in that revision as well as the new files? > Your >>> strace shows old revs file being opened, a revision that simply adds >>> files would not read old revision files. >>> >>> >> >> I said in the previous email that the problem replicates after i >> create a new repository and init and sync! >> >> i.e. >> >> svnadmin create ... >> svnsync init ... >> svnsync sync ... >> >> FAILS > > As far as I can see you have still failed to answer the question. After > > svnadmin create ... > svnsync init ... > svnsync sync ... FAIL > > does a subsequent > > svnsync sync ... > > fail? That's a second sync on the same repository as the first sync > without a second create or a second init. > > -- > uberSVN: Apache Subversion Made Easy > http://www.uberSVN.com >
