Active File Management error logs
Some errors occur during the replication. These errors impact the replication. You can check information about the errors that are logged in the /var/adm/ras/mmfs.log.latest file.
| Error | Description | User action |
|---|---|---|
| E_PERM (1) | Operation not permitted. This error occurred when an operation that is limited to processes with appropriate privileges or to the owner of a file or other resources is performed. | Check the appropriate privileges for the complete path. Running operation can be requeued. Report this issue. |
| E_NOENT (2) | No file or directory found. A component of a specified named path did not exist. | A file or a directory is deleted. Check the path. Running operation can be requeued. Report this issue. |
| E_INTR (4) | Interrupted system call error. An asynchronous signal was caught by the process during the execution of an interruptible function. This error occurs when the recovery is in-progress and the gateway node is interrupted. | You can reset operations that are running operations. Report this error if it occurs regularly. |
| E_IO (5) | Input/output error. Some physical or network input or output error occurred. The same file descriptor is lost (over written or by any subsequent errors). | Check the file and its valid attribute. It might be a temporary error, and it might not occur in a subsequent operation. |
| E_ACCES (13) | Permission denied error. An attempt was made to access a file that is forbidden by its file access permissions. | Check the permission for the complete path. Running operation can be requeued. Report this issue. |
| E_EXIST (17) | File exists error. This error is logged when a file or a directory exist at other site and failed to replace due to compatibility. | Check the file and its valid attribute. Running operation can be requeued. Report this issue. |
| E_ISDIR (20) | Not a directory error. A component of a specified file path existed, but it was not a directory, when a directory was expected. | Running operation can be requeued. Report this issue. |
| E_INVAL (22) | Invalid argument error. Some invalid argument was supplied. This error occurs when input is invalid for processing. | Running operation can be requeued. Report this issue. |
| E_ROFS (30) | Read-only file system. An attempt was made to modify a file or a directory on a file system that was read-only at the time. | Check the path. Running operation can be requeued. Report this issue. |
| E_RANGE (34) | Result too large. A numerical result of the function was too large to fit in the available space (might have exceeded precision). | Running operation can be requeued. Report this issue. |
| E_STALE (52) | File system or mount path is not accessible or connection is reset. | Check the home path from the cache. It is a temporary failure and can be resolved when the home or home fileset is accessible. |
| E_OPNOTSUPP (64) | Operation not supported. The attempted operation is not supported for the type of object referenced. Usually, this error occurs when a file descriptor refers to a file or socket that cannot support this operation. | Running operation can be requeued. Report this issue. |
| E_TIMEDOUT (78) | Operation timed out. A connect or send request failed because the user did not properly respond after a time. The timeout period depends on the communication protocol, and also network is overloaded and the replication does not get enough bandwidth. | It is a temporary error and can be succeeded in next operation. |
| E_DQUOT (88) | Disc quota exceeded error. It occurs when the disc quota exhaust. | Check and increase the disc quota. It is a temporary failure and can be resolved in a next access. |
| E_NOATTR (112) | No attribute found. A file or directory does not have an attribute to access the file. The file is no longer valid and not accessible. | Check the file and its valid attribute. Running operation can be requeued. Report this issue. |
| E_DAEMON_DEATH (307) | This error is logged when daemon is interrupted and failed to service. | All running operations can be interrupted. Report this issue. |
| E_NODE_FAILED (734) | This error occurs because of the RPC failure. The sender was notified by the config manager that the RPC destination failed. | Running operation can be requeued. Report this issue. |
| E_NOT_MOUNTED(753) | File system was not mounted. This error can be logged because of this issue. | Check the path. Running operation can be requeued. Report this issue. This error is resolved when the file system is mounted back. |
| E_CACHE_CONFLICT (755) | Cache file and original are not synchronized. Handling depends on the current conflict semantics. | Check the file and its valid attribute. Running operation can be requeued. Report this issue. |
| E_REQUEUED (765) | Conflict error in the replication. It occurs when a replication operation does not find correct action and fails to replicate. | Running operation can be requeued. Report this issue. |
| E_PANIC (666) | This error occurs because of an unrecoverable error. | Running operation can be requeued. Report this issue. |
| E_REMOTEIO (1121) | Remote I/O error. Home or home fileset is not accessible. This error occurs because the
special ctl operation is failed. |
Check the home path from the cache. It is a temporary failure and can be resolved when the home or home fileset is accessible. |