| Name | Data Type | Default Value | Qualifiers |
| Name | Data Type | Value |
| DirectoryServiceUsage | uint16 | |
| Description | string | This enumerated integer specifies if the filesystem supports security principal information and therefore requires support from a file server that uses one or more directory services. If the filesystem requires such support, there must be a concrete subclass of Dependency between the LocalFileSystem element and the specified file server ComputerSystem.
The enumerated values are:
"Not Used" indicates that the filesystem will not support security principal information and so will not require support from a directory service.
"Optional" indicates that the filesystem may support security principal information. If it does, it will require support from a directory service and the Dependency association described above must exist.
"Required" indicates that the filesystem supports security principal information and will require support from a directory service. The Dependency association described above must exist. |
| ValueMap | string | 0, 1, 2, 3, 4 |
| Values | string | Unknown, Other, Not Used, Optional, Required |
| LocalAccessDefinitionRequired | uint16 | |
| Description | string | This enumerated integer specifies if the provider requires that a file system device be made locally accessible before it can be used as a file system. If local access is required to be set up, a vendor could provide a default mechanism, for instance, making "/dev/fs1" available as "/etc/mounts/fs1" automatically in an Unix-like OS, but it can be overridden by the system administrator.If local access is not required, the file system is automatically made available by some default name (for instance, the volume at "C" is also the filesystem "C:"on Windows systems, and cannot be overridden. |
| ValueMap | string | 0, 1, 2, 3, 4 |
| Values | string | Unknown, Other, Required, Required -- vendor default, Not Required |
| MultipleDisksSupported | uint16 | |
| Description | string | This enumerated integer specifies if the file system type is capable of being built on multiple LogicalDisks. If "Supported", the provider can make differential use of the capabilities of the underlying multiple logical disks, for instance, by putting file system meta data on one kind of LogicalDisk and placing file data on another.
The CIM_LocalFileSystem can only reside on a single LogicalDisk,but that LogicalDisk could be built up from multiple underlying logical disk using an appropriate profile. This property specifies support for capabilities that make use of that sub-structure. |
| ValueMap | string | 0, 1, 2, 3 |
| Values | string | Unknown, Other, Supported, Not Supported |
| PathNameSeparatorString | string | |
| Description | string | The string is used by this FileSystem for constructing a path name from the sequence of directories that leads to some contained LogicalFile (file or directory). Currently the most commonly used are '\' for Windows and '/' in Unix. |