CreateDir - File Storage NAS - Alibaba Cloud Documentation Center

Creates a directory in a file system.

Operation description

Only General-purpose Network File System (NFS) file systems support this operation.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
nas:CreateDir	create	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
FileSystemId	string	Yes	The ID of the file system.	31a8e4****
RootDirectory	string	Yes	The directory name. The directory must start with a forward slash (/). The directory can contain digits and letters. The directory can contain underscores (_), hyphens (-), and periods (.). The directory cannot contain symbolic links, such as the current directory (.), the upper-level directory (..), and other symbolic links. Note If the root directory does not exist, configure the information for directory creation. The system then automatically creates the specified root directory based on your settings. If the root directory exists, you do not need to configure the information for directory creation. The configurations for directory creation are ignored even if you configure the information.	test
OwnerUserId	integer	Yes	The owner ID for the directory. Valid values: 0 to 4294967295.	1
OwnerGroupId	integer	Yes	The ID of the owner group for the directory. Valid values: 0 to 4294967295.	123
Permission	string	Yes	The Portable Operating System Interface (POSIX) permissions applied to the root directory. The value is a valid octal number, such as 0755.	0755
Recursion	boolean	No	Specifies whether to create a multi-level directory. Valid values: true (default): If no multi-level directory exists, directories are created level by level. false: Only the last level of directory is created. An error message is returned because the parent directory does not exist.	true

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	BC7C825C-5F65-4B56-BEF6-98C56C7C****

Examples

Sample success responses

JSONformat

{
  "RequestId": "BC7C825C-5F65-4B56-BEF6-98C56C7C****"
}

Error codes

HTTP status code	Error code	Error message
403	InvalidProtocolType.NotSupported	The specified protocol type does not supported.

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2024-09-05	The Error code has changed	View Change Details