On Sep 7, 2013, at 19:24, Nico Kadel-Garcia wrote:
> > http://www.pbs.org/wgbh/evolution/library/01/6/l_016_08.html
>
> *Do not do this* with write access repositories, is my advice from knowledge
> of NFS filesystems. Writes, and partial writes, can occur from one host for
> the next "commit"
> http://www.pbs.org/wgbh/evolution/library/01/6/l_016_08.html
*Do not do this* with write access repositories, is my advice from
knowledge of NFS filesystems. Writes, and partial writes, can occur from
one host for the next "commit" but not actually be seen on the next "round
robin" server until
Hi,
On Sat, Sep 07, 2013 at 05:50:29PM +0530, Nitin Bhide wrote:
>Philip/Stefan/Andreas,
>
>Thanks for the help. I was able to write a small python script
>specific to
>my needs and recover the repository. It was corrupted revision
>property
>file. I have written the detai
Hello, Lev.
You wrote 7 сентября 2013 г., 16:02:19:
LS> FAQ says, that it should work, but for me it doesn't see WC as WC at all:
Oh, sorry for noise, "rpc.lockd" crashed and I didn't notice that.
--
// Black Lion AKA Lev Serebryakov
Philip/Stefan/Andreas,
Thanks for the help. I was able to write a small python script specific to
my needs and recover the repository. It was corrupted revision property
file. I have written the details in blog post.
http://nitinbhide.blogspot.in/2013/09/recovering-from-corrupted-subversion.html
Hello, Users.
FAQ says, that it should work, but for me it doesn't see WC as WC at all:
% mount | grep /usr/home
192.168.134.2:/usr/home on /usr/home (nfs)
% svn status
svn: warning: W155007: '/usr/home/lev/FreeBSD/ports' is not a working copy
% ls -la | grep svn
drwxr-xr-x 4 lev lev 512
Hi,
Ivan Zhakov and I checked the minidump but the only thing we could find
using the dump is that the application fails when writing an error message.
So some error occurred while producing the log, but we dont know which
and somehow the handling corrupted the error stat
