Я нашёл более красивое решение
Совершено случайно наткнулся на описание ошибок
-601 FFFFFDA7 NO SUCH ENTRY
Source: eDirectory or NDS
Explanation: The specified eDirectory or NDS object could not be found on the eDirectory or NDS server that is responding to a request.
WARNING: Applying all solutions mentioned in this topic could make the problem worse if the actual cause of the problem is not known. Before following a course of action, make sure that you understand the cause of the error and the consequences for the actions suggested.
Possible Cause: The object name entered could not be found in the context specified. The object name might be mistyped. The context for the workstation might be incorrect for the object being sought. The leading dots or trailing dots might be used incorrectly.
Action: Check the context specified for the object name entered. If the command line input was the object name, check the workstation's context. Make sure that it points to the correct level of the eDirectory or NDS tree for the object name specified. If the input includes the object's full or partial context, make sure that the leading and trailing dots are specified appropriately and the types are correct.
Possible Cause: Occurrences of this error in response to an eDirectory or NDS or bindery API can occur during normal handling of an eDirectory or NDS tree. However, continuous occurrences of this error might indicate a program fault in the application being used.
Action: If the error persists, contact the developer of the application.
Possible Cause: If this error occurs in response to a request for the target server to start replica synchronization in eDirectory or NDS, the partition root object that was specified is not present on the target server.
Action: If you are running ds.nlm v5.01 or later, the error in this case will resolve itself.
If using an earlier version of the NLM program, do the following:
Verify the state of the replicas.
Make sure the time is synchronized on all file servers in the tree.
Remove the replica, and then add it again. This step could be dangerous and should be a last solution.
Possible Cause: An attempt was made to finish eDirectory or NDS authentication for an eDirectory or NDS object, and the object was deleted before the authentication was completed.
Action: In this case, the error is informational and no action is required.
Possible Cause: This error could occur in the background process of eDirectory or NDS backlinker. The external reference might have been removed or overwritten by an incoming replica. This error occurs if the external reference was removed or overwritten while eDirectory or NDS was waiting for the backlink attribute to be created on an eDirectory or NDS server that is holding a replica of the eDirectory or NDS partition that includes the externally referenced object.
Action: Ignore transitory occurrences. Over a period of time, the error will resolve itself in this case.
Possible Cause: This error could occur in response to a dead or rename obituary during the eDirectory or NDS Janitor background process. In this case, the error could occur while processing obituaries after a successful completion of the background process for eDirectory or NDS replica synchronization. If it does, then it means the target server does not hold an external reference of the object being deleted.
The external reference might have been removed or overwritten by an incoming replica.
Action: If the server itself is no longer in the tree but still exists as an object in the tree, then locate the server object and delete it.
If the replica is incoming, then it should get updated into the replica ring and should be notified and should correct itself. If the error does not correct itself in this case, contact a Novell Support Provider.
Possible Cause: An attempt was made to read information for an eDirectory or NDS object that does not exist on the eDirectory or NDS server that is replying to the request.
Possible Cause: If the error displays while running DSTRACE on the server or while viewing Partition Continuity in NDS manager, it usually means that an entry is missing from the entry record table on the source server.
Action: Make sure the request has had enough time to be processed on the eDirectory or NDS server.
Identify which object is returning the -601 error. To do this, use the set DSTRACE=+sync command on both the source and the target server and on any other servers in the replica list.
If the object with the error is not a server object, try deleting it.
If the object with the error is a server object, see if DSTRACE returns any other errors besides -601. Address those errors, if any.
You can use the Partition Continuity feature of NDS manager to evaluate the partition for synchronization errors. NDS manager has several repair functions that allow you to correct synchronization errors without having to run DSREPAIR from the server.
NOTE: Using the Send Updates option might create high levels of network traffic.
If Partition Continuity shows no errors besides -601, use NDS manager to send updates from a replica that does not have the error, or receive updates on the replica with the error.
NOTE: Receive updates will create less traffic than send. Send Updates and Receive Updates are available from the Tree view, the list of Partitions and Servers, and the Partition Continuity view in NDS manager.
Possible Cause: The replicas of an eDirectory or NDS partition might be inconsistent.
Action: If the problem is with the replica ring being inconsistent, see actions for error -672 FFFFFD60 NO ACCESS.
WARNING: Using the Send All Objects option or the Receive All Objects option might create high levels of network traffic.
If the problem is with inconsistencies inside the partition, such as objects on different replicas not being the same, use the Send All Objects option or Receive All Objects option in DSREPAIR to update replicas of a partition on the servers holding replicas.
Пересоздание реплики спасло.
Теперь можно более точно строить предположение о происходивших глюках
Хотя, занятие довольно бессмысленное и почти не выполнимое
Удалось спасти положение и на этом спасибо
Теперь на собственноё шкуре испытал отказоустойчивость eDir
До сих пор как-то не доводилось.
P.S
Корень, откуда можно искать описание ошибок
http://www.novell.com/documentation/nwec/index.html
