| [ENOTDIR] |
| | A component of the name2 prefix is not a directory. |
| [ENAMETOOLONG] |
| | A component of either pathname exceeded 255 characters, or the entire length of either path name exceeded 1023 characters. |
| [ENOENT] |
| | The named file does not exist. |
| [EACCES] |
| | A component of the name2 path prefix denies search permission. |
| [ELOOP] |
| | Too many symbolic links were encountered in translating the pathname. |
| [EEXIST] |
| | The path name pointed at by the name2 argument already exists. |
| [EIO] | An I/O error occurred while making the directory entry for name2, or allocating the inode for name2, or writing out the link contents of name2. |
| [EROFS] |
| | The file name2 would reside on a read-only file system. |
| [ENOSPC] |
| | The directory in which the entry for the new symbolic link is being placed cannot be extended because there is no space left on the file system containing the directory. |
| [ENOSPC] |
| | The new symbolic link cannot be created because there is no space left on the file system that will contain the symbolic link. |
| [ENOSPC] |
| | There are no free inodes on the file system on which the symbolic link is being created. |
| [EDQUOT] |
| | The directory in which the entry for the new symbolic link is being placed cannot be extended because the user’s quota of disk blocks on the file system containing the directory has been exhausted. |
| [EDQUOT] |
| | The new symbolic link cannot be created because the user’s quota of disk blocks on the file system that will contain the symbolic link has been exhausted. |
| [EDQUOT] |
| | The user’s quota of inodes on the file system on which the symbolic link is being created has been exhausted. |
| [EIO] | An I/O error occurred while making the directory entry or allocating the inode. |
| [EFAULT] |
| | The name1 or name2 argument points outside the process’s allocated address space. |
|
