Posted 29 April 2015 - 02:42 PM
It is very hard to track down what causes them.
There is almost 100% repeatability when using reconcile command when new files were added.
They often occurs when user interupts a long-lasting commands.
But some users get orphaned files despite of not using any of previously described methods.
The current environment consists of one Hybrid Server and one Edge Server (used to be 2).
I would be grateful for pointing how I can debug it and/or in which cases orphaned files may occur.
The files can be easily unlocked with "unlock -x" command. Nevertheless the sudden appearance of 130k of such files over night can mean problems in the configuration.
Posted 29 April 2015 - 04:44 PM
Posted 13 May 2015 - 12:09 PM
p4 opened -x //depot/dir/subdir/...shows a lot of
//depot/dir/subdir/file.ext - user@workspace *orphaned*messages
Posted 25 May 2015 - 12:43 PM
There are considerably less orphan locks on 2014.1 which is not to say there no more and we have a hard time understanding what the cause is.
Posted 25 May 2015 - 01:10 PM
We are using 2013.3/770073
Posted 10 August 2015 - 10:44 AM
We will upgrade soon but now I have to deal with it on 2013.3 version.
Also tagged with one or more of these keywords: distributed, edge server, orphaned
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users