MKDIR(2) BSD System Calls Manual MKDIR(2)NAMEmkdir — make a directory file
mkdir(const char *path, mode_t mode);
The directory path is created with the access permissions specified by
mode and restricted by the the umask(2) of the calling process.
The directory's owner ID is set to the process's effective user ID. The
directory's group ID is set to that of the parent directory in which it
A 0 return value indicates success. A -1 return value indicates an
error, and an error code is stored in errno.
ERRORSMkdir() will fail and no directory will be created if:
[ENOTDIR] A component of the path prefix is not a directory.
[EINVAL] The pathname contains a character with the high-order bit
A component of a pathname exceeded 255 characters, or an
entire path name exceeded 1023 characters.
[ENOENT] A component of the path prefix does not exist.
[EACCES] Search permission is denied for a component of the path pre‐
[ELOOP] Too many symbolic links were encountered in translating the
[EPERM] The path argument contains a byte with the high-order bit
[EROFS] The named file resides on a read-only file system.
[EEXIST] The named file exists.
[ENOSPC] The new directory cannot be created because there is no space
left on the file system that will contain the directory.
[ENOSPC] There are no free inodes on the file system on which the
directory is being created.
[EDQUOT] The new directory cannot be created because the user's quota
of disk blocks on the file system that will contain the
directory has been exhausted.
[EDQUOT] The user's quota of inodes on the file system on which the
directory is being created has been exhausted.
[EIO] An I/O error occurred while making the directory entry or
allocating the inode.
[EIO] An I/O error occurred while reading from or writing to the
[EFAULT] Path points outside the process's allocated address space.
SEE ALSOchmod(2), stat(2), umask(2)STANDARDSMkdir() conforms to IEEE Std 1003.1-1988 (“POSIX”).
4.2 Berkeley Distribution December 11, 1993 4.2 Berkeley Distribution