hadoop mfs

• [-R] — Enables recursion allowing you to perform the operation in subdirectories as well.
• <path> — Specifies the path to the file or directory.

You cannot delete specific access types with this parameter. Instead, if necessary, reset the value for the specific access type to an empty string using the -setace parameter. If you use an empty string to deny a specific type of access, then that type of access is denied to all users. To deny specific types of access to specific users only, use the negation operator (!). The mode bits corresponding to the ACEs being deleted, do not change.

• [-R] — (Optional) Enables recursion allowing you to perform the operation in subdirectories as well.
• <path> — (Required) Specifies the path to the file or directory.

If one or more ACEs are available for the file or directory, a plus sign (+), which indicates that both ACEs and POSIX mode bits are set for the given file or directory, is returned. If the ACE on the file or directory is an empty string, the plus sign is not returned.

<target>

File name, including the full path, of the file to link to.

<hardlink>

New name, including the full path, of the file to link with.

• Chunks used for each file
• Server where each chunk resides
• Whether compression is enabled for each file
• Whether encryption is enabled for each file
• Whether audit is enabled (A) or disabled (U) for each file

• Whether compression is enabled for the directory (indicated by z )
• The configured chunk size (in bytes) for the directory.

Use this option when there are millions of files in a directory. In this scenario. using this option results in the fastest listing of files, as only the fids and the file names are returned. All other file attributes are ignored.

• Whether compression is enabled for each file
• Whether encryption is enabled for each file
• Whether audit is enabled (A) or disabled (U) for each file

• Chunks used for each file
• Server where each chunk resides

• Overwrite existing values with new values, if specified, for access types that were previously set.
• Set new values for access types that have not yet been set.
• Not set or modify access types that were not passed in with the command, whether they were previously set or unset.

Specify the ACEs immediately after the -setace parameter. Specify all the other parameters, after the ACE.

-R

Enables recursion allowing you to perform the operation in subdirectories as well. Recursion is enabled only if -R is specified; if -R is not specified, sets or modifies the permissions for the given directory only.

<ace>

ACE Syntax defined using boolean expressions and sub-expressions.

-readfile

-writefile

-executefile

Specifies permissions (defined using ACEs) for reading, writing, or executing the file.

-readdir

-lookupdir

Specifies permissions (defined using ACEs) for accessing the directory. To permit users to read files in the directory, grant the lookupdir access permission. To permit users to write to or execute files in the directory, grant the readdir and lookupdir access permissions.

-addchild

-deletechild

Specifies permissions (defined using ACEs) for adding or deleting subdirectories.

-aces

Specifies ACEs as a single string. Specify a comma-separated list of ACEs within quotes, up to 60 KB in length. You can set the following permissions.

rf	Refers to read file access.
wf	Refers to write file access
ef	Refers to execute file access
rd	Refers to read directory access. To write to or execute files in the directory, grant the user rd and ld permissions.
ld	Refers to lookup directory access. To read the files in the directory, grant the user ld access. To write to or execute files in the directory, grant the user both rd and ld permissions.
ac	Refers to add child directory access.
dc	Refers to delete child directory access.

-preservemodebits

Indicates whether to preserve or modify POSIX mode bits. Values can be:

• true - preserve existing POSIX mode bits
• false - change POSIX mode bits to match the given ACE setting

The default value is false.

-setinherit

Indicates whether or not to allow all files and subdirectories under the specified directory to inherit the ACE of the parent directory. Values can be:

• true - inherit ACE from parent
• false - do not inherit ACE from parent

The default value is true.

If true, new files and directories under the parent directory,inherit the ACEs and corresponding POSIX mode bits from the parent directory.

If false, files and directories under the parent directory do not inherit the ACE of the parent directory. Instead, by default, the files and directories get the default ACE, which is the empty string for all access types; POSIX mode bits are set on the files and directories in the traditional way.

<path>

Specifies the path to the file or directory.

Enabling auditing of a directory does not enable auditing of files and subdirectories that exist in the directory. You must enable auditing on those existing files and subdirectories. However, any new files and subdirectories that you create will automatically be enabled for auditing. See How Does Auditing Work?.

For operations on the object to be logged, auditing also needs to be enabled on the cluster and the volume in which the object is located. See Managing Auditing for details. If auditing is enabled for a directory, new files and directories created within that directory are also enabled for auditing.

• on — turns on compression using the default algorithm (LZ4)
• lzf — turns on compression and sets the algorithm to LZF
• lz4 — turns on compression and sets the algorithm to LZ4
• zlib — turns on compression and sets the algorithm to ZLIB

The path is required and specifies the path (to the file) on which to run the command. The output fields for this command are as follows.

• Contains local data, returns the following final output:

  File has local data

• Is completely offloaded, returns the following final output:

  File does not have local data

mode

A text string indicating the read, write, and execute permissions for the owner, group, and other permissions. See also Managing Permissions.

compression

• U: uncompressed
• L: LZf
• Z (Uppercase): LZ4
• z (Lowercase): ZLIB

replication

The replication factor of the file (directories display a dash instead)

owner

The owner of the file or directory

group

The group of the file of directory

size

The size of the file or directory

date

The date the file or directory was last modified

chunk size

The chunk size of the file or directory

name

The name of the file or directory

chunk

The chunk number. The first chunk is a primary chunk labeled "p", a 64K chunk containing the root of the file. Subsequent chunks are numbered in order.

fid

The chunk's file ID, which consists of three parts:

• The ID of the container where the file is stored
• The inode of the file within the container
• An internal version number

For volume links, the first fid is the chunk that stores the volume link itself; the fid after the arrow (->) is the first chunk in the target volume.

host

The host on which the chunk resides. When several hosts are listed, the first host is the first copy of the chunk, while subsequent hosts are replicas.

target volume name

The name of the volume pointed to by a volume link.

writability

Displays whether the volume is writable.

The may not always be updated. For more information, see the UpdateTimeInterval entry in volume create.

• regular
• directory
• symlink
• vollink
• kvstore
• device

regular

• FSTRegBucket
• FSTRegCF
• FSTRegKeyMap

kvstore

• FSTKvTable
• FSTKvTabletMap
• FSTKvSchema
• FSTKvTablet
• FSTKvSegMap
• FSTKvSpillMap
• FSTKvKeyMap
• FSTKvXattr

device

• FSTDevPipe
• FSTDevSocket
• FSTDevBlock
• FSTDevChar

For all other types, subtypes are not valid.