8.4. Adding POSIX Compliant File System Storage
8.4.1. Attaching POSIX Compliant File System Storage
POSIX file system support allows you to mount file systems using the same mount options that you would normally use when mounting them manually from the command line. This functionality is intended to allow access to storage not exposed using NFS, iSCSI, or FCP.
Any POSIX compliant file system used as a storage domain in Red Hat Virtualization must be a clustered file system, such as Global File System 2 (GFS2), and must support sparse files and direct I/O. The Common Internet File System (CIFS), for example, does not support direct I/O, making it incompatible with Red Hat Virtualization.
Do not mount NFS storage by creating a POSIX compliant file system storage domain. Always create an NFS storage domain instead.
Attaching POSIX Compliant File System Storage
- Click → .
- Click New Domain.
- Enter the Name for the storage domain.
Select the Data Center to be associated with the storage domain. The Data Center selected must be of type POSIX (POSIX compliant FS). Alternatively, select
Datafrom the Domain Function drop-down list, and
POSIX compliant FSfrom the Storage Type drop-down list.
If applicable, select the Format from the drop-down menu.
- Select a host from the Use Host drop-down list.
Enter the Path to the POSIX file system, as you would normally provide it to the
Enter the VFS Type, as you would normally provide it to the
mountcommand using the
man mountfor a list of valid VFS types.
Enter additional Mount Options, as you would normally provide them to the
mountcommand using the
-oargument. The mount options should be provided in a comma-separated list. See
man mountfor a list of valid mount options.
Optionally, you can configure the advanced parameters.
- Click Advanced Parameters.
- Enter a percentage value in the Warning Low Space Indicator field. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged.
- Enter a GB value in the Critical Space Action Blocker field. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked.
- Select the Wipe After Delete check box to enable the wipe after delete option. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
- Click OK.