Re: Reference to non-existent node

Davor Josipovic writes: >> Are you running Linux or Windows? Is the disk local or networked? > > Server is Debian 9.3. Disk is mounted through fstab with options > noatime,nodiratime,data=ordered,nofail. > >> Do you have some other process running that mointors the filesystem or >> the repositor

Re: Reference to non-existent node

> Are you running Linux or Windows? Is the disk local or networked? Server is Debian 9.3. Disk is mounted through fstab with options noatime,nodiratime,data=ordered,nofail. > Do you have some other process running that mointors the filesystem or > the repository? Does it actively delete files?

Re: Reference to non-existent node

> Are you running Linux or Windows? Is the disk local or networked? Server is Debian 9.3. Disk is mounted through fstab with options noatime,nodiratime,data=ordered,nofail. > Do you have some other process running that mointors the filesystem or > the repository? Does it actively delete files?

Re: Reference to non-existent node

> Are you running Linux or Windows? Is the disk local or networked? Server is Debian 9.3. Disk is mounted through fstab with options noatime,nodiratime,data=ordered,nofail. > Do you have some other process running that mointors the filesystem or > the repository? Does it actively delete files?

Re: Reference to non-existent node

Davor Josipovic writes: >> Do you see the DELETE in the log after the failed MERGE? Was there an >> error? > > The apache2 log I posted is the whole log for that day as far as I > recall. There was nothing else. You see the DELETE error before the > MERGE error. I think that is due to a timing i

Re: Reference to non-existent node

> Do you see the DELETE in the log after the failed MERGE? Was there an > error? The apache2 log I posted is the whole log for that day as far as I recall. There was nothing else. You see the DELETE error before the MERGE error. I think that is due to a timing issue. In my previous tries (there

Re: Reference to non-existent node

> Do you see the DELETE in the log after the failed MERGE? Was there an > error? The apache2 log I posted is the whole log for that day as far as I recall. There was nothing else. You see the DELETE error before the MERGE error. I think that is due to a timing issue. In my previous tries (there

Re: Reference to non-existent node

> Do you see the DELETE in the log after the failed MERGE? Was there an > error? The apache2 log I posted is the whole log for that day as far as I recall. There was nothing else. You see the DELETE error before the MERGE error. I think that is due to a timing issue. In my previous tries (there

Re: enhancement suggestion

On 20.02.2018 15:59, Johan Corveleyn wrote: > On Tue, Feb 20, 2018 at 1:11 PM, Christian Klie wrote: >> Hello, >> currently I made a huge commit. In respect of the number of the files (see >> attachment "working copy"). >> While the commit went down the transaction grew and grew and grew (see >> a

Re: enhancement suggestion

On Tue, Feb 20, 2018 at 1:11 PM, Christian Klie wrote: > Hello, > currently I made a huge commit. In respect of the number of the files (see > attachment "working copy"). > While the commit went down the transaction grew and grew and grew (see > attachment "transaction"). > That all happend becaus

Save the date: ApacheCon North America, September 24-27 in Montréal

Dear Apache Enthusiast, (You’re receiving this message because you’re subscribed to a user@ or dev@ list of one or more Apache Software Foundation projects.) We’re pleased to announce the upcoming ApacheCon [1] in Montréal, September 24-27. This event is all about you — the Apache project com

Re: Bugreport: invalid xml file produced by: svn log --xml --verbose --use-merge-history --search "msg1"

Hi all, I entered this bug to the issue tracker last year: https://issues.apache.org/jira/browse/SVN-4711 Should I also post it to the development list (d...@subversion.apache.org )? Thanks On 13.12.2017 10:08, Johan Corveleyn wrote: +1

enhancement suggestion

Hello, currently I made a huge commit. In respect of the number of the files (see attachment "working copy"). While the commit went down the transaction grew and grew and grew (see attachment "transaction"). That all happend because of the files in the transaction's folder being very small but h

Re: Reference to non-existent node

Johan Corveleyn writes: >> [Sat Feb 10 03:25:30.640591 2018] [dav:error] [pid 2966] [client >> X.X.X.X:61712] Could not MERGE resource "/svn/repo/!svn/txn/463-e8" into >> "/svn/repo/repofolder". [500, #0] >> [Sat Feb 10 03:25:30.642889 2018] [dav:error] [pid 2966] [client >> X.X.X.X:6171

Re: Not so cheap moves

Johan Corveleyn escribió el 20/02/2018 10:57:46: > On Tue, Feb 20, 2018 at 10:35 AM, Ignacio González (Eliop) > wrote: > > "Branko Čibej" wrote: > >> On 19.02.2018 15:40, Ignacio González (Eliop) wrote: > >>> Client svn 1.8.13 > >>> Server svn 1.8.13 on Centos 7 64 bit > >>> - > >>> I have a

Re: Not so cheap moves

On Tue, Feb 20, 2018 at 10:35 AM, Ignacio González (Eliop) wrote: > "Branko Čibej" wrote: >> On 19.02.2018 15:40, Ignacio González (Eliop) wrote: >>> Client svn 1.8.13 >>> Server svn 1.8.13 on Centos 7 64 bit >>> - >>> I have a repository with 400 000 revisions. >>> Proyect X in that repositor

re: Not so cheap moves

"Branko Čibej" wrote: > On 19.02.2018 15:40, Ignacio González (Eliop) wrote: >> Client svn 1.8.13 >> Server svn 1.8.13 on Centos 7 64 bit >> - >> I have a repository with 400 000 revisions. >> Proyect X in that repository has the usual trunk / branches / tags >> structure. >> Tags are structure

[no subject]

"Branko Čibej" wrote: > On 19.02.2018 15:40, Ignacio González (Eliop) wrote: >> Client svn 1.8.13 >> Server svn 1.8.13 on Centos 7 64 bit >> - >> I have a repository with 400 000 revisions. >> Proyect X in that repository has the usual trunk / branches / tags >> structure. >> Tags are structure