Note: The information contained in this article is structured as help information for the System Management Interface Tool (SMIT) and is not intended for general reading.
A file system is a hierarchical structure (file tree) of files and directories. This type of structure resembles an inverted tree with the roots at the top and the branches at the bottom. This file tree uses directories to organize data and programs into groups, allowing the management of several directories and files at one time.
Lists all file systems as well as displays characteristics of file systems, such as name, mount point, type, size, and automatic mounts.
Displays characteristics of file systems, such as mount points, automatic mounts, permissions, and file system size.
You can add, change, show, or delete any of the file system types the operating system supports. These include the following:
You can add, change, show, or delete any of the file system types the operating system supports. These include the following:
You can add, change, show, or delete any of the file system types the operating system supports. These include the following:
This file system uses database journaling techniques to maintain its structural consistency. This prevents damage to the file system when the system is halted abnormally.
Creates a file system on a logical volume within a previously created volume group. A new logical volume is created for the file system.
The volume group on which to create the file system. A volume group is a collection of one or more physical volumes.
The volume group on which to create the file system. A volume group is a collection of one or more physical volumes.
The size of the Journaled File System. You can specify size in units of 512-byte blocks, Megabytes or Gigabytes. If the specified size cannot be divided evenly by the physical partition size, it is rounded up to the closest number that can be evenly divided.
The maximum size of a JFS file system is a function of its fragment size and the number of bits per i-node (NBPI) value. These values yield the following size restrictions:
NBPI Maximum value in
512 byte blocks Megabytes Gigabytes
512 16777216 8192 8
1024 33554432 16384 16
2048 67108864 32768 32
4096 134217728 65536 64
The mount point, which is the directory where the file system is available or will be made available.
The mount point, which is the directory where the file system is available or will be made available.
Indicates whether the file system is mounted at each system restart. Possible values are:
Indicates whether the file system is mounted at each system restart. Possible values are:
Sets the permissions for the file system.
The security-related mount options. You can specify the following values:
Enables disk accounting on this file system.
The file system fragment size. The values you can specify are: 512, 1024, 2048, or 4096. The default fragment size is 4096 bytes.
A file system fragment is the smallest unit of disk storage that can be allocated to a file. If your system has a large number of small files, decreasing the fragment size will increase the efficiency of disk utilization. However, decreasing the fragment size could also decrease file access efficiency.
The ratio of file system size, in bytes, to the number of i-nodes. Increasing the number of bytes per i-node (NBPI) decreases the total number of i-nodes in a file system.
The Allocation Group size determines the allowed range of NBPI values for a file system according to the following table:
Allocation Group Size NBPI Range 8 512, 1024, 2048, 4096, 8192, 16384 16 1024, 2048, 4096, 8192, 16384, 32768 32 2048, 4096, 8192, 16384, 32768, 65536 64 4096, 8192, 16384, 32768, 65536, 131072
The compression algorithm for the file system. You can select the following choices:
no - Creates a file system that does not use data compression. The default is no.
LZ - Create a file system in which all data is automatically compressed using LZ compression before being written to disk and is automatically uncompressed when read from disk. Requires a fragment size of less than 4096 bytes.
NOTE: A file system that has been created using LZ cannot be changed to no.
Adds a journaled file system (JFS) to an existing logical volume. The size of the file system will be the size of the logical volume. All data on the target logical volume is destroyed.
The name of an existing logical volume. You can specify the name of a logical volume, or select it from a list of previously defined logical volumes.
Note: All data on this logical volume will be destroyed.
The name of an existing logical volume. You can select a logical volume from a list of previously defined logical volumes.
Note: All data on the selected logical volume will be destroyed.
Displays file system attributes and allows you to modify certain attributes.
Removes a file system, any logical volume on which it resides, and the associated stanza in the /etc/filesystems file.
The name of the file system that is being removed.
The name of the file system that is being removed.
Selecting yes removes the mount point (directory) where the file system is normally made available.
NOTE: The directory is removed only if it is empty.
Makes a CD-ROM file system available by adding an appropriate stanza to the /etc/filesystems file. This eases management of the CD-ROM file systems.
Removes a CD-ROM file system and the associated stanza in the /etc/filesystems file.
The device name of the CD-ROM device.
Attempts to reduce external fragmentation by reallocating disk blocks and consolidating small unusable holes of disk space into larger contiguous free space. The defragmentation utility offers these options:
External file system fragmentation occurs when files are allocated and deleted; this can produce small holes of free disk space that are not contiguous. These holes may be too small to satisfy a given allocation request. In extreme cases, this can result in a file system with a large percentage of its free space occupying holes that are essentially unusable.
Instructs the operating system to make a file system available for use at a specified location (the mount point).
Mounts a file system expressed as a device (for example, /dev/hd6). Use the SMIT List function to obtain a list of file systems.
The specified directory becomes the root directory of the newly mounted file system. You can select a directory from a list of file systems.
Requests a forced mount during system initialization to enable mounting over the root file system.
The remote node that holds the directory to be mounted.
Mounts a file system as a removable file system. While there are open files on it, a removable mounted file system behaves the same as a normally mounted file system. However, when there are no open files (and while no process has a current directory on the file system), all of the file system disk buffers in the file system are written to the medium, and the operating system forgets the structure of the file system.
Mounts a file system as a read-only file system, regardless of its previous specification.
Determines device access from this mount. Selecting yes prevents devices from being opened from this mount.
Determines whether execution of setuid and setgid programs are allowed from this mount. Selecting yes prevents execution of these programs from this mount.
Mounts all stanzas in the /etc/filesystems file that contain the type=Type attribute and are not mounted.
The name of the group.
Unmounts a previously mounted file system, directory, or file. Members of the system group and users operating with root user authority can unmount any mounted directory. Other users can unmount any directory or file if they have write permission to the mounted-over directory or file.
Note: SMIT will not unmount the /usr/lpp/info/$LANG directory, the directory on which SMIT helps are located. Typically, this is the CD-ROM.
Unmounts all mounted file systems, except those with stanzas in the /etc/filesystems file with the mount=automatic attribute.
Unmounts all remotely mounted file systems.
To unmount local mounts, you can specify the device, directory, file, or file system on which it is mounted.
The node holding the mounted directory you want to unmount.
Unmounts all stanzas in the /etc/filesystems file that contain the type=Type flag and are mounted.
Checks for file system inconsistencies. You must be able to read the device file that the file system resides on (for example, the /dev/lv00 device). Normally, the file system is consistent, and this option merely reports on the number of files, used blocks, and free blocks in the file system. If the file system is inconsistent, this option displays information about the inconsistencies found.
Any inconsistencies reported and not fixed by this SMIT menu interface must be addressed by running fsck interactively from the command line.
The file system to verify. If you do not specify a file system, the /etc/filesystems file is examined to find a list of file systems to check by default. This option can perform simultaneous checks on multiple file systems. This can reduce the time required to check a large number of file systems.
Performs a fast check. Under normal circumstances, the only file systems likely to be affected by halting the system without shutting down properly are those that are mounted when the system stops.
Specifies a file parameter as a scratch file on a file system other than the one being checked.
Creates copies of your files on a backup medium, such as a magnetic tape or diskette. The copies are in one of the two following backup formats:
Creates a copy of your file system on a backup medium, such as a magnetic tape or diskette. The copy is in backup-by-i-node format.
The file system that is being backed up.
The output device to which the file system is backed up.
The level of backup to create. You can specify 0 for a full backup, or a numeral from 1 to 9 for an incremental backup. A level n backup backs up all files changed since the most recent level n-1 (or lower) backup. For example, a level 3 backup backs up all files changed since the most recent level 2 backup. The default backup level is 0.
Determines whether to record the current backup in /etc/dumpdates. Selecting yes saves information needed for maintaining incremental backups. The default is no.
Restore files backed up on a local system.
Restores contents of a file system backup (also known as a backup by i-node).
The input device. Specify the device parameter as a file name (such as the /dev/rmt0 file) to get input from the named device, or specify - (minus) to get input from the standard input device.
The directory from which to begin the restore. You must be at the top of the file system you are restoring; for example, if you are restoring /home, you must be in /home.
Determines whether to produce verbose output.
The number of 512-byte blocks to read in a single input operation. If you do not specify this flag, the restore command selects a default value appropriate for the physical device you have selected. Larger values of the blocks parameter result in larger physical transfers from tape devices.
Lists the contents of a backup. The backup can be in either backup-by-i-node format or backup-by-name format.
You can back up files and directories to an archive, or you can restore or list contents of an archive.
Creates copies of your files, directories, or both on a backup medium, such as a magnetic tape or diskette. The copies (or archive) are in back-up-by-name format.
Specifies one or more files, directories, or both to back up. Type a period (".") to back up everything in the current working directory. Backing up a directory recursively backs up the contents of that directory including all subdirectories.
The directory from which to begin the backup. This allows for specifying path names relative to the current working directory to back up.
Select "Yes" to back up only the files belonging to the Journaled File System (JFS). Select "No" to back up all files.
Select "Yes" to pack (compress) files before placing them in the archive. Some files cannot be compressed and will be placed in the archive as is. Restoring the archive will automatically unpack files packed by this option. Select "No" to not pack files.
Restores the contents of an archive in back-up-by-name format.
The particular file or directory to restore. To restore the entire archive, leave this field empty. The file or directory name you specify must match the name stored in the archive. Use the List Contents of a Backup menu option to determine file or directory names in a particular archive.
Specify the file system fragment size in bytes. Decreasing the fragment size below a full block (4096 bytes) allows partial blocks to be allocated at the end of a file. You can set the fragment size to 512, 1024, 2048, or 4096 bytes. If a file system is compressed, you must specify a fragment size of 512, 1024, or 2048 bytes.
Creates a file system. The resulting file system is compatible with the AIX Version 3 file system if you accept the default values for fragment size, number of bytes per i-node (NBPI), and allocation group size and if the file system size remains below 2GB.
Creates a file system in which all data is compressed automatically using LZ compression before being written to disk and all data is uncompressed automatically when read from disk.
Creates a file system in which the maximum file size is increased from 2GB to 64GB minus 124MB.
The size of the file system. You can specify size in units of 512-byte blocks, Megabytes, or Gigabytes. If the value begins with a "+", it is interpreted as a request to increase the file system size by the specified amount. If the specified size cannot be evenly divided by the physical partition size, it is rounded up to the closest number that can be evenly divided.
The unit size for the input provided for the size of the file system. Possible values are Megabytes, Gigabytes, and 512bytes. The default value is Megabytes.
The size of the file system in terms of the value selected in the Unit Size field.
The file system block size in bytes. You can set the block size to 512, 1024, 2048, or 4096 bytes. A smaller block size uses less disk space for small files, but may degrade performance.
Specifies that the journal log for the file system is within the file system.
The size, in MBytes, for the optional inline journal log. The default is the size of the file system divided by 256.
The size of the J2 File System. You can specify size in units of 512-byte blocks, Megabytes, or Gigabytes. If the specified size cannot be evenly divided by the physical partition size, it is rounded up to the closest number that can be evenly divided.
Enables large files for the file system.
Determines whether the file system is mounted at each system restart. You can select the following values:
Determines whether the file system is mounted at each system restart. You can select the following values:
Back up only files that have been modified since a specific full backup (an incremental backup).
The possible levels are 0 to 9. If you do not supply a level, the default is 9. A level 0 backup includes all files on the file system. An n level backup includes all files modified since the last n - 1 level backup.
The physical device name (the block or raw name), the name of the directory on which the file system is normally mounted, or the name of any other directory.
The name of the file system or the directory within the file system to be backed up.
The number of 512-byte blocks to write in a single output operation, referred to as the block size. If a number is not specified, the backup command uses a default value appropriate for the physical device selected. Larger values result in larger physical transfers to tape devices.
Running the backup command results in the loss of all material previously stored on the selected output medium.
Limits the total number of blocks to use on the backup medium. Use this attribute for diskette devices only. This option is ignored when performing i-node backups.
Causes the backup command to display a report on each phase of the backup as it is completed and gives regular progress reports during the longest phase.
You can set or change a file system's size, permissions, mount point, and automatic mounts.
The name of the file system, expressed as a mount point.
The name of the file system, expressed as a mount point.
The name of the file system, expressed as a mount point.
The name of the file system, expressed as a mount point.
The new mount point, which is the directory where the file system is available or will be made available.
The new mount point, which is the directory where the file system is available or will be made available.
Sets the permissions for the file system:
ro - Specifies read-only permissions.
rw - Specifies read-write permissions.
The mount group. Mount groups are used to group related mounts so that they can be mounted as one instead of mounting each individually. For example, if several scratch file systems always need to be mounted together when performing certain tests, they can each be placed in the test mount group.
The mount group. Mount groups are used to group related mounts so that they can be mounted as one instead of mounting each individually. For example, if several scratch file systems always need to be mounted together when performing certain tests, they can each be placed in the test mount group.
This file system uses database journaling techniques to keep its structure consistent. This prevents damage to the file system if the system is halted abnormally. The enhanced JFS supports both 32-bit and 64-bit file system semantics. It supports 4 petabyte file systems and dynamically allocates inodes so that disk space is not wasted on unused inodes.
Adds an enhanced journaled file system (JFS2) and creates a new logical volume for it.
Adds an enhanced journaled file system (JFS2) to an existing logical volume. The size of the file system is the size of the logical volume. All data on the target logical volume is destroyed.
Create a snapshot for an Enhanced Journaled File System.
The recommended size of your snapshot is between two percent and 15 percent of the size of your selected file system.
Specify whether the size of the snapshot is in 512-byte blocks, megabytes (MB) or gigabytes (GB).
Specify the number of units for the snapshot. The type of unit is specified with the Unit Size option.
Name the file system you want to create a snapshot of.
Lists any snapshots that already exist for the specified file system.
Allows you to increase the size of the specified external snapshot.
Select the snapshot whose size you want to change.
Specify the storage device on which the snapshot is stored.
Create a snapshot for an Enhanced Journaled File System and make a backup of the snapshot image.
Specify the path for the mount point of the snapshot.
Specify whether or not you want the snapshot removed after the backup is completed.
This option applies only to external snapshots. Internal snapshots are automatically mounted along with the owning file system. They are accessible through the directory <fs>/.snapshot.
Mounting the external snapshot allows you access to the snapshot so that you can compare contents at the time of the snapshot with those at any other point in time, retrieve a file or set of files that were later lost or modified, and to compare the contents of a file from one time period to another.
The snapshot is mounted with read-only permissions.
Specify whether you want to remove the logical volume associated with the specified snapshot.
Unmount the specified external snapshot.
Create a snapshot for the specified file system and perform a backup by inode of the snapshot image.
Create a snapshot for a file system on a previously defined logical volume.
Create a snapshot of a JFS2 file system and perform a backup by name from the snapshot.
Specifies the JFS2 snapshot and the logical volume on which it resides that you want to remove.
Extends or shrinks the file system to a specific size or by a specified amount. You can specify the size value in 512-byte blocks, Megabytes (M) or Gigabytes (G).
To increase the file system size by a specific amount, place a plus sign (+) in front of the specified value. To decrease a file system size by a specific amount, place a minus sign (-) in front of the specified value. To increase the file system size, specify a value larger than the current size. To reduce the file system size, specify a value smaller than the current size. If the specified size is not evenly divisible by the physical partition size, it is rounded up to the closest number that is evenly divisible.
The format used for storing named extended attributes in the JFS2 filesystem. Version 2 provides support for scalable named extended attributes and support for NFS4 ACLs. Version 1 is compatible with AIX version 5.2 or earlier. The default is Version 1.
The format used for storing named extended attributes in the JFS2 filesystem. Version 2 provides support for scalable named extended attributes and support for NFS4 ACLs. Version 1 is compatible with AIX version 5.2 or earlier. The default is Version 1.
The format used for storing named extended attributes in the JFS2 filesystem. Version 2 provides support for scalable named extended attributes and support for NFS4 ACLs. Version 1 is compatible with AIX version 5.2 or earlier.
Includes extended attributes and ACLs in the backup. The backup can only be restored on AIX version 5.3 or later. Select "yes" to back up extended attributes. Select "no" to exclude the extended attributes. The default is "yes".
Includes extended attributes and ACLs in the backup. The backup can only be restored on AIX version 5.3 or later. Select "yes" to back up extended attributes. Select "no" to exclude the extended attributes. The default is "yes".
Includes extended attributes and ACLs in the backup. The backup can only be restored on AIX version 5.3 or later. Select "yes" to back up extended attributes. Select "no" to exclude the extended attributes. The default is "yes".
Restores any extended attributes or ACLs that are in the archive. Select "yes" to include the extended attributes. Select "no" to exclude the extended attributes. The default is "yes".
Includes extended attributes and ACLs in the backup. The backup can only be restored on AIX version 5.3 or later. Select "yes" to back up extended attributes. Select "no" to exclude the extended attributes. The default is "yes".
Restores any extended attributes or ACLs that are in the archive. Select "yes" to include the extended attributes. Select "no" to exclude the extended attributes. The default is "yes".
Includes extended attributes and ACLs in the backup. The backup can only be restored on AIX version 5.3 or later. Select "yes" to back up extended attributes. Select "no" to exclude the extended attributes. The default is "yes".
Includes extended attributes and ACLs in the backup. The backup can only be restored on AIX version 5.3 or later. Select "yes" to back up extended attributes. Select "no" to exclude the extended attributes. The default is "yes".
Restores any extended attributes or ACLs that are in the archive. Select "yes" to include the extended attributes. Select "no" to exclude the extended attributes. The default is "yes".
The logical volume to be used for the logging device for the new file system. Selecting INLINE specifies that the journal log for the file system is within the file system itself.
The logical volume to be used for the logging device for the new file system.
You can set storage limits (quotas) for individual users or groups on a per-filesystem basis. The quota system issues a warning to the user when a particular quota is exceeded, but allows some extra space for current work. Remaining over quota repeatedly at logout eventually results in further allocation attempts being denied until the total usage is reduced below the user's or group's quota.
Specifies that file and block usage statistics be maintained and limits enforced by the file system for a particular quota type or for all types.
Information on current quota usage, limits, and grace periods can be displayed for any number of users or groups.
For an Enhanced Journaled File System you can enable or disable quota management, stop or restart quota limit enforcement, display quota usage within file systems, or manage quota limits classes.
Specify the name of a quotas-enabled Enhanced Journaled File System to which the quota limits for this user will apply.
Specify the name of a quotas-enabled Enhanced Journaled File System to which the quota limits for this group will apply.
Specify the user whose quota limits you want to change or view. The user must already exist on the system. To change a user's quota limits, you must have the correct access privileges.
Specify the group whose quota limits you want to change or view. The group must already exist on the system. To change a group's quota limits, you must have the correct access privileges.
Block usage and limit information can be displayed and modified in units of kilobytes, megabytes, or gigabytes. The specified units apply to all block allocation fields.
The soft limit defines the number of disk blocks or files that can be accumulated under normal operations. The hard limit defines the maximum amount of disk blocks or files that can be accumulated on a temporary basis. The quota grace period specifies the amount of time the soft limit can be exceeded.
If usage remains above the soft limit beyond the specified grace period, the soft limit will be interpreted as the hard limit and no further allocation will be allowed. This condition can be reset by removing disk blocks or files to reduce usage below the soft limit.
You can specify block limits in kilobytes, megabytes, or gigabytes, and grace periods in days, hours, minutes or seconds.
You can specify grace periods in units of days, hours, minutes or seconds. If usage remains above the soft limit beyond the specified grace period, the soft limit will be interpreted as the hard limit and no further allocation will be allowed. This condition can be reset by removing disk blocks or files to reduce usage below the soft limit.
The users for which to display quota usage information. The users must already exist on the system.
If you do not specify any users, quota usage information is displayed for your user ID. You must have superuser authority to list quota usage information for other users.
To enter the list of users, type in a string containing the user names (separating the names with spaces), or use the F4 List box to select the names from the choices displayed. When you select, the string of names is displayed in the field in the correct format.
The groups for which to display quota usage information. The groups must already exist on the system.
If you do not specify any groups, quota usage information is displayed for your primary group ID. You must have superuser authority to list quota usage information for other groups.
To enter the list of groups, type in a string containing the group names (separating the names with spaces), or use the F4 List box to select the names from the choices displayed. When you select, the string of names is displayed in the field in the correct format.
You can enable Quota Management on individual Enhanced Journaled File Systems.
When enabled, disk block allocation and file usage statistics begin to be recorded. Quota Limits Enforcement is started immediately, and automatically each time the file system is mounted. When Quota Management is first enabled for a file system, all users and groups are members of the default Limits Class, which initially allows unlimited usage. Change the default Limits Class and optionally add additional Limits Classes in order to restrict disk block and file usage within a file system.
When disabled, disk block allocation and file usage statistics are no longer recorded and Quota Limits are not enforced. You can temporarily stop Quota Limits Enforcement without disabling Quota Management.
Select an Enhanced Journaled File System on which to enable or disable Quota Management.
You can enable Quota Management for a specific quota type or for all types. You can disable Quota Management for the file system. If you select "no", all quota types are disabled. When disabled, disk block allocation and file usage statistics are no longer recorded, and Quota Limits are not enforced. You can temporarily stop Quota Limits Enforcement without disabling Quota Management.
You can temporarily stop Quota Limits Enforcement for a particular Enhanced Journaled File System. While stopped, disk block and file usage statistics continue to be maintained for the selected file system, but allocation is not bound by the Limits Classes defined for that file system until Quota Limits Enforcement is restarted.
Once restarted, any new disk block and file allocation will be bound by the Limits Classes for that file system.
Select an Enhanced Journaled File System on which to stop or restart Quota Enforcement.
You can stop or restart Quota Enforcement for an specific quota type or for all types.
Prints a summary of quota usage and limits for specified file systems.
Select a set of Enhanced Journaled File Systems for which to display a summary of quota usage and limits. You can also type the list of file systems, separated by spaces.
Specify a particular quota type or "all" to print a summary for all quota types.
Specify whether report header lines should be printed before the summary for each file system.
Disk block and file usage statistics should be recalculated whenever there is a potential discrepancy between the recorded and actual statistics. Statistics are recalculated automatically when Quota Management is enabled. This task should be performed manually whenever a file system has been unmounted abnormally (for example, due to a power failure or system crash).
Select an Enhanced Journaled File System on which to examine all existing files and directories and calculate the total disk block and file usage for each quota type. The amount of time it takes to complete this task depends on the number of files and directories which must be examined.
NOTE: Disk block and file usage statistics are recalculated automatically when Quota Management is enabled for a file system.
Specify whether file and block usage statistics will be recalculated for a particular quota type, or all types.
Specify whether to report discrepancies between the calculated and recorded usage statistics.
Create a Limits Class with the block usage, file usage, and grace period limits that you specify. Users or groups assigned to a Limits Class are bound by the limits defined by that Class. Any users or groups not assigned to a Class are bound by the Default Limits Class.
Select an Enhanced Journaled File System for this Limits Class.
Select the quota type for this Limits Class.
For a particular Limits Class, the soft limit defines the number of disk blocks or files that can be accumulated by each member of that Class under normal operations. The hard limit defines the maximum amount of disk blocks or files that can be accumulated on a temporary basis. The quota grace period specifies the amount of time the soft limit can be exceeded.
If usage for a member of the Class remains above the soft limit beyond the specified grace period, the soft limit will be interpreted as the hard limit and no further allocation will be allowed for that member. This condition can be reset by removing disk blocks or files to reduce usage below the soft limit.
You can specify block limits in kilobytes, megabytes, or gigabytes, and grace periods in days, hours, minutes or seconds.
You can specify block limits can in kilobytes, megabytes, or gigabytes.
You can specify grace periods in days, hours, minutes or seconds.
Shows the attributes for a specific Limits Class. If you have the correct access privileges, you can change certain attribute values of the Limits Class.
Select the ID for this Limits Class.
Select the name for this Limits Class.
Changes the default Limits Class values to those of the specified Limits Class. Any users or groups not assigned to a Class are bound by the Default Limits Class.
Assign a user or group to a specific Limits Class for a file system. Users or groups assigned to a Limits Class are bound by the limits defined in that Class. Any users or groups not assigned to a Class are bound by the Default Limits Class.
Specify the user to assign as a member of this Limits Class.
Specify the group to assign as a member of this Limits Class.
Select an Enhanced Journaled File System for which to display a list of defined Limits Classes.
Removes a Limits Class from a file system. Removing a Limits Class deletes the attributes defined for that Class, but does not affect the disk block or file usage statistics for members of that Class. Members of the deleted Class will be bound by the default Limits Class until they are assigned to another Class.
Indicates the number of blocks currently allocated by this user or group. If usage remains above the soft limit beyond the specified grace period, the soft limit will be interpreted as the hard limit and no further allocation will be allowed. This condition can be reset by removing disk blocks or files to reduce usage below the soft limit.
Indicates the number of files currently allocated by this user or group. If usage remains above the soft limit beyond the specified grace period, the soft limit will be interpreted as the hard limit and no further allocation will be allowed. This condition can be reset by removing disk blocks or files to reduce usage below the soft limit.
By default, only those file systems in which the user or group has disk blocks or files allocated are included in the report. Other options are to include file systems with no allocated storage, or to restrict the set of file systems to those with usage over quota.
Specifies whether inode extents smaller than the default size of 16 kb can be created on the target filesystem. The small inode extents will only be created when there is not 16 kb of contiguous file system space available. A filesystem with this option enabled cannot be accessed on prior releases of AIX.
Enable Encrypted File System support for a JFS2 filesystem. Once this option is set to yes for a JFS2 filesystem it cannot be changed.
Critical EFS information of file system, directories and files will be backed up.
Critical EFS information of directories and files will be backed up.
The key store will allow the user to utilize files in Encrypted File System. The selection of file will create a key store file associated with this user. It is recommended that file is selected. Select none for no key store to be created. All other EFS (efs_*) attributes will not have any effect.
Indicates where the efs_admin key store can be found when user opens its key store. This can be file, to indicate /etc/security/efs/efs_admin/key store.
The efs_initalks_mode of admin allows for root or other security privileged system users to reset the user's key store password. Otherwise, if the user forgets their key store password, they will not be able to access their Encrypted File System files.
If the guard mode is selected, then root cannot reset the user's key store password.
This option specifies the algorithm for the user's key within the key store. This key will protect the encrypting key of files the user creates within the Encrypted File System.
RSA_1024 = 1024bit RSA key
RSA_2048 = 2048bit RSA key
RSA_4096 = 4096bit RSA key
When an encrypted file is created in an Encrypted File System, this option specifies the algorithm and mode in which the file will be encrypted.
AES_128_CBC = Advanced Encryption Standard with 128 bit key length, in Cipher Block Chaining mode.
AES_128_EBC = Advanced Encryption Standard with 128 bit key length, in Electronic Code Book mode.
AES_192_CBC = Advanced Encryption Standard with 192 bit key length, in Cipher Block Chaining mode.
AES_192_ECB = Advanced Encryption Standard with 192 bit key length, in Electronic Code Book mode.
AES_256_CBC = Advanced Encryption Standard with 256 bit key length, in Cipher Block Chaining mode.
AES_256_ECB = Advanced Encryption Standard with 256 bit key length, in Electronic Code Book mode.
Remove the specified snapshot.
Create an internal snapshot for an Enhanced Journaled File System. The snapshot will use space in the specified file system and be accessible through the <fs>/.snapshot directory.
The name for the snapshot being created. The access for the snapshot will be a directory with the snapshot name in the .snapshot directory in root of the file system specified.
Remove the specified internal snapshot. This will free the space used by the snapshot in the owning file system and make the snapshot no longer accessible.
The name of the snapshot being deleted.
Restores the file system to the point-in-time image preserved by the specified snapshot.
The name of the snapshot to revert the file system to.
Create an internal snapshot for an Enhanced Journaled File System and make a backup of the snapshot image. The snapshot created will be created within the file system.
Create an external snapshot for an Enhanced Journaled File System and make a backup of the snapshot image. The snapshot created will be created in a separate logical volume.
Specify yes if you want to create snapshots for the file system inside the file system. This option is not compatible with releases earlier than 6.1. Specify no if you want snapshots created for the file system to be in separate logical volumes.