File system events
The following table lists the events that are created for the File System component.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| clear_mountpoint_tip | TIP | INFO | no | Message: File system {0} was unmounted or mounted at its default mountpoint. |
| Description: Clear any previous tip for this file system about using a non- default mountpoint. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| desc_disk_quorum_fail | STATE_CHANGE DEGRADED |
WARNING | no | Message: Sufficient healthy descriptor disks are not found for file system {0} quorum. |
| Description: Sufficient healthy descriptor disks are not found. | ||||
| Cause: Sufficient healthy descriptor disks are not found. No quorum is found for the file system. | ||||
| User Action: Check the health state of disks, which are declared as descriptor disks for the file system. An insufficient number of healthy descriptor disks might lead to a data access loss. For more information, see the 'Disk issues' section in the 'Problem Determination Guide'. | ||||
| desc_disk_quorum_ok | STATE_CHANGE HEALTHY |
INFO | no | Message: Sufficient healthy descriptor disks are found for file system {0} quorum. |
| Description: Sufficient healthy descriptor disks are found. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| exported_fs_available | STATE_CHANGE HEALTHY |
INFO | no | Message: The file system {0} used for exports is available. |
| Description: A file system used for export is available. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| exported_path_available | STATE_CHANGE HEALTHY |
INFO | no | Message: All NFS or SMB exported path with undeclared mount points are available. |
| Description: All NFS or SMB exported path are available, which may include automounted folders. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| exported_path_unavail | STATE_CHANGE DEGRADED |
WARNING | no | Message: At least for one NFS or SMB export ({0}), no GPFS file system is mounted to the exported path. |
| Description: At least for one NFS or SMB exported path the intended file system is unclear or unmounted. Those exports cannot be used and can lead to a failure of the service. | ||||
| Cause: At least one NFS or SMB exported path does not point to a mounted GPFS file system according to /proc/mounts. The intended file system is unknown because the export path does not match the default mountpoint of any GPFS file system due to the use autofs or bind-mount. | ||||
| User Action: Check the mount states for NFS and SMB exported file systems. This message can be related to autofs or bind-mounted file systems. | ||||
| filesystem_found | ADD_ENTITY | INFO | no | Message: File system {0} was found. |
| Description: A file system listed in the IBM Storage Scale configuration was detected. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| filesystem_vanished | DEL_ENTITY | INFO | no | Message: File system {0} has vanished. |
| Description: A file system listed in the IBM Storage Scale configuration was not detected. | ||||
| Cause: A file system, listed in the IBM Storage Scale configuration as mounted before, is not found. This can be a valid situation. | ||||
| User Action: To verify that all expected file systems are mounted, run the mmlsmount all_local -L command. | ||||
| fs_forced_unmount | STATE_CHANGE FAILED |
ERROR | no | Message: The file system {0} was {1} (forced) to unmount. |
| Description: A file system was forced to unmount by IBM Storage Scale. | ||||
| Cause: A situation, like a SGPanic or a quorum loss can initiate the unmount process. | ||||
| User Action: Check error messages and error log for further details. For more information, see the 'File system forced unmount' topic in the 'Problem Determination Guide'. | ||||
| fs_maintenance_mode | STATE_CHANGE SUSPENDED |
INFO | no | Message: File system {id} is set to maintenance mode. |
| Description: The file system is in maintenance mode. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| fs_preunmount_panic | STATE_CHANGE FAILED |
ERROR | no | Message: The file system {0} is unmounted because of an SGPanic situation. |
| Description: A file system is unmounted because of an SGPanic situation. | ||||
| Cause: A file system is set to preunmount state because of an SGPanic situation. | ||||
| User Action: For more information, check error messages and error log in the mmfs.log file. | ||||
| fs_remount_mount | STATE_CHANGE_EXTERNAL HEALTHY |
INFO | no | Message: The file system {0} was mounted {1}. |
| Description: A file system was mounted. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| fs_unmount_info | INFO | INFO | no | Message: The file system {0} was unmounted {1}. |
| Description: A file system was unmounted. | ||||
| Cause: A file system was unmounted. | ||||
| User Action: N/A | ||||
| fs_working_mode | STATE_CHANGE HEALTHY |
INFO | no | Message: File system {id} is not in maintenance mode. |
| Description: The file system is not in maintenance mode. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| fserrallocblock | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Corrupted alloc segment is detected while attempting to allocate a disk block. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check the error message and the mmfs.log.latest log for details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbadaclref | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: File references indicate invalid ACL. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbaddirblock | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Invalid directory block detected. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbaddiskaddrindex | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Bad disk index is detected in disk address. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbaddiskaddrsector | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Bad sector number in disk address or start sector plus length would exceed the disk size. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbaddittoaddr | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Invalid ditto address is detected. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbadinodeorgen | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Deleted inode has dir entry or the generation number do not match to the directory. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbadinodestatus | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Inode status is bad, and is expected to indicate deleted status. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbadptrreplications | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Invalid computed pointer indicates replication factors. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message for details and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbadreplicationcounts | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Invalid current, or maximum data or metadata replication counts. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrbadxattrblock | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Indicates invalid extended attribute block. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrcheckheaderfailed | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: CheckHeader returned an error. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrclonetree | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Invalid cloned in file tree structure. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrdeallocblock | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Corrupt allocated segment is detected while attempting to deallocate disk block. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrdotdotnotfound | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Unable to locate an entry. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrgennummismatch | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Found generation number in '..' entry does not match actual generation number of parent directory. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrinconsistentfilesetrootdir | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Inconsistent fileset or root directory, which means fileset is inUse, root dir '..' points to itself. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrinconsistentfilesetsnapshot | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Inconsistent fileset or snapshot records, which means fileset snapList points to a SnapItem that doesn't exist. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrinconsistentinode | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Size data in inode is inconsistent. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrindirectblock | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Indirect block header does not match info in inode. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrindirectionlevel | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Indicates invalid indirection level in inode. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrinodecorrupted | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Code to catch infinite loop in the lfs layer in case of a corrupted inode or directory entry. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrinodenummismatch | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Found inode number in '..' entry does not match actual inode number of parent directory. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrinvalid | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Unknown error={2}. |
| Description: Unrecognized FSSTRUCT error received. Check IBM documentation. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrinvalidfilesetmetadatarecord | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Indicates invalid fileset metadata record. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrinvalidsnapshotstates | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Indicates invalid snapshot states, which means more than one in an inode space being emptied (SnapBeingDeletedOne). | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrsnapinodemodified | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Inode was modified without saving old content to shadow inode file. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fserrvalidate | STATE_CHANGE DEGRADED |
ERROR | FTDC upload | Message: FS={0},ErrNo={1},Msg={2}. |
| Description: Validation routine has failed on a disk read. | ||||
| Cause: A file system corruption is detected. | ||||
| User Action: Check error message and the mmfs.log.latest log for further details. For more information, see the 'Checking and repairing a file system' topic in the 'Administration Guide'. If the file system is severely damaged, then follow the steps mentioned in the 'MMFS_FSSTRUCT' section in the 'Problem Determination Guide'. | ||||
| fsstruct_fixed | STATE_CHANGE HEALTHY |
INFO | no | Message: A file system {id} structure error has been marked as fixed. |
| Description: A file system structure error was declared or detected as fixed. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ill_exposed_fs | STATE_CHANGE DEGRADED |
WARNING | no | Message: The file system {0} has a data exposure risk as there are file(s) where all replicas are on suspended disks, which makes it vulnerable to potential data loss when a disk fails. |
| Description: A configuration change is causing the file system to have a data exposure risks. | ||||
| Cause: The mmfsadm eventsExporter get fs <filesystem> command reports that the file system has a data exposure risk. | ||||
| User Action: Run the mmrestripefs command against the file system. | ||||
| ill_replicated_fs | STATE_CHANGE DEGRADED |
WARNING | no | Message: The file system {0} is not properly replicated. |
| Description: A configuration change is causing the file system to no longer being properly replicated. | ||||
| Cause: The mmfsadm eventsExporter get fs <filesystem> command reports that the file system is no longer being properly replicated. | ||||
| User Action: Run the mmrestripefs command against the file system. | ||||
| ill_unbalanced_fs | TIP | TIP | no | Message: The file system {0} is not properly balanced. |
| Description: A configuration change is causing the file system to no longer being properly balanced. | ||||
| Cause: The mmfsadm eventsExporter get fs <filesystem> command reports that the file system is no longer properly balanced. | ||||
| User Action: Run the mmrestripefs command against the file system. | ||||
| inode_high_error | STATE_CHANGE FAILED |
ERROR | no | Message: The inode usage of fileset {id[1]} in file system {id[0]} reached a nearly exhausted level. {0}. |
| Description: The inode usage in the fileset reached a nearly exhausted level. | ||||
| Cause: The inode usage in the fileset reached a nearly exhausted level. | ||||
| User Action: Run the mmdf command and the mmlsfileset -i -L commands to check the inode consumption. Run the mmchfileset command to increase the inode space. Refer to the Monitoring > Events page in the IBM Storage Scale GUI to fix this event with the help of a directed maintenance procedure. Select the event from the list of events and select Actions > Run Fix Procedure to launch the DMP. | ||||
| inode_high_warn | STATE_CHANGE DEGRADED |
WARNING | no | Message: The inode usage of fileset {id[1]} in file system {id[0]} has reached a warning level. {0}. |
| Description: The inode usage in the fileset has reached warning level. | ||||
| Cause: The inode usage in the fileset has reached warning level. | ||||
| User Action: Delete data. | ||||
| inode_no_data | STATE_CHANGE UNKNOWN |
INFO | no | Message: No inode usage data is used for fileset {id[1]} in file system {id[0]}. |
| Description: No inode usage data is used in performance monitoring. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| inode_normal | STATE_CHANGE HEALTHY |
INFO | no | Message: The inode usage of fileset {id[1]} in file system {id[0]} reached a normal level. |
| Description: The inode usage in the fileset reached a normal level. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| inode_removed | STATE_CHANGE HEALTHY |
INFO | no | Message: No inode usage data is used for fileset {id[1]} in file system {id[0]}. |
| Description: No inode usage data is used in performance monitoring. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| local_exported_fs_unavail | STATE_CHANGE FAILED |
ERROR | no | Message: The local file system {0} that is used for exports is not mounted. |
| Description: A local file system that is used for export is not mounted. | ||||
| Cause: A local file system for a declared export is not available. | ||||
| User Action: Check the local mounts. | ||||
| low_disk_space_info | INFO | INFO | no | Message: Low disk space. StoragePool {1} in file system {0} has reached the threshold as configured in a migration policy. |
| Description: Low disk space. A file system reached the threshold as configured in a migration policy. | ||||
| Cause: A lowDiskSpace callback was received. A file system has reached its high occupancy threshold. | ||||
| User Action: For more information, check warning message and the mmfs.log.latest log. Check also https://www.ibm.com/docs/en/spectrum- scale/5.1.2?topic=policies-using-thresholds-migrate-data-between-pools . | ||||
| low_disk_space_warn | STATE_CHANGE DEGRADED |
WARNING | no | Message: Low disk space. File system {0} has reached its high occupancy threshold. StoragePool={1}. |
| Description: Low disk space. A file system has reached its high occupancy threshold. | ||||
| Cause: Low disk space. A file system has reached its high occupancy threshold. | ||||
| User Action: For more information, check the warning message and the mmfs.log.latest log. Clear this event by using the mmhealth event resolve low_disk_space_warn <fsname> command . | ||||
| mounted_fs_check | STATE_CHANGE HEALTHY |
INFO | no | Message: The file system {0} is mounted. |
| Description: A mounted file system is reported correctly. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| no_disk_space_clear | STATE_CHANGE HEALTHY |
INFO | no | Message: A disk space warning has been marked as fixed. A disk space issue was resolved. |
| Description: A file system low disk or inode space warning was declared or detected as resolved. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| no_disk_space_inode | STATE_CHANGE FAILED |
ERROR | no | Message: Fileset {2} runs out of space. Filesystem={0}, StoragePool={1}, reason={3}. |
| Description: A fileset runs out of inode space. | ||||
| Cause: A fileset does not have sufficient inode space. Triggered by the 'noDiskSpace' callback. | ||||
| User Action: For more information, check the error message and the mmfs.log.latest log. Clear this event by using the mmhealth event resolve no_disk_space_inode <fsname> command . | ||||
| no_disk_space_warn | STATE_CHANGE FAILED |
ERROR | no | Message: File system {0} runs out of space. StoragePool={1}, FSet={2}, reason={3}. |
| Description: A file system runs out of disk space. | ||||
| Cause: A file system does not have sufficient disk space. Triggered by the 'noDiskSpace' callback. | ||||
| User Action: For more information, check the error message and the mmfs.log.latest log. Clear this event by using the mmhealth event resolve no_disk_space_warn <fsname> command . | ||||
| not_default_mountpoint | TIP | TIP | no | Message: The mountpoint for file system {0} differs from the declared default value. |
| Description: The mountpoint differs from the declared default value. | ||||
| Cause: The mountpoint differs from the declared default value. | ||||
| User Action: Review your file system configuration. | ||||
| ok_exposed_fs | STATE_CHANGE HEALTHY |
INFO | no | Message: The file system {0} has no data exposure risk. |
| Description: The file system has no data exposure risk. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ok_replicated_fs | STATE_CHANGE HEALTHY |
INFO | no | Message: The file system {0} is properly replicated. |
| Description: The file system is properly replicated. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| ok_unbalanced_fs | STATE_CHANGE HEALTHY |
INFO | no | Message: The file system {0} is properly balanced. |
| Description: The file system is properly balanced. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| pool-data_high_error | STATE_CHANGE FAILED |
ERROR | no | Message: The pool {id[1]} of file system {id[0]} has reached a nearly exhausted data level. {0}. |
| Description: The pool has reached a nearly exhausted level. | ||||
| Cause: The pool has reached a nearly exhausted level. | ||||
| User Action: For more information, add more capacity to pool or move data to different pool or delete data and/or snapshots. | ||||
| pool-data_high_warn | STATE_CHANGE DEGRADED |
WARNING | no | Message: The pool {id[1]} of file system {id[0]} has reached a warning level for data. {0}. |
| Description: The pool has reached a warning level. | ||||
| Cause: The pool has reached a warning level. | ||||
| User Action: For more information, add more capacity to pool or move data to different pool or delete data and/or snapshots. | ||||
| pool-data_no_data | STATE_CHANGE UNKNOWN |
INFO | no | Message: No usage data for pool {id[1]} in file system {id[0]}. |
| Description: No pool usage data in performance monitoring. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| pool-data_normal | STATE_CHANGE HEALTHY |
INFO | no | Message: The pool {id[1]} of file system {id[0]} has reached a normal data level. |
| Description: The pool has reached a normal level. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| pool-data_removed | STATE_CHANGE HEALTHY |
INFO | no | Message: No usage data for pool {id[1]} in file system {id[0]}. |
| Description: No pool usage data in performance monitoring. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| pool-metadata_high_error | STATE_CHANGE FAILED |
ERROR | no | Message: The pool {id[1]} of file system {id[0]} has reached a nearly exhausted metadata level. {0}. |
| Description: The pool has reached a nearly exhausted level. | ||||
| Cause: The pool has reached a nearly exhausted level. | ||||
| User Action: Add more capacity to pool or move data to different pool or delete data and/or snapshots. | ||||
| pool-metadata_high_warn | STATE_CHANGE DEGRADED |
WARNING | no | Message: The pool {id[1]} of file system {id[0]} has reached a warning level for metadata. {0}. |
| Description: The pool has reached a warning level. | ||||
| Cause: The pool has reached a warning level. | ||||
| User Action: Add more capacity to pool or move data to different pool or delete data and/or snapshots. | ||||
| pool-metadata_no_data | STATE_CHANGE UNKNOWN |
INFO | no | Message: No usage data for pool {id[1]} in file system {id[0]}. |
| Description: No pool usage data in performance monitoring. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| pool-metadata_normal | STATE_CHANGE HEALTHY |
INFO | no | Message: The pool {id[1]} of file system {id[0]} has reached a normal metadata level. |
| Description: The pool has reached a normal level. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| pool-metadata_removed | STATE_CHANGE HEALTHY |
INFO | no | Message: No usage data for pool {id[1]} in file system {id[0]}. |
| Description: No pool usage data in performance monitoring. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| pool_high_error | STATE_CHANGE FAILED |
ERROR | no | Message: The pool {id[1]} of file system {id[0]} has reached a nearly exhausted level. {0}. |
| Description: The pool has reached a nearly exhausted level. | ||||
| Cause: The pool has reached a nearly exhausted level. | ||||
| User Action: Add more capacity to pool or move data to different pool or delete data and/or snapshots. | ||||
| pool_high_warn | STATE_CHANGE DEGRADED |
WARNING | no | Message: The pool {id[1]} of file system {id[0]} reached a warning level. {0}. |
| Description: The pool has reached a warning level. | ||||
| Cause: The pool has reached a warning level. | ||||
| User Action: Add more capacity to pool or move data to different pool or delete data and/or snapshots. | ||||
| pool_no_data | INFO | INFO | no | Message: The state of pool {id[1]} in file system {id[0]} is unknown. |
| Description: Cannot determine fill state of the pool. | ||||
| Cause: Cannot determine fill state of the pool. | ||||
| User Action: N/A | ||||
| pool_normal | STATE_CHANGE HEALTHY |
INFO | no | Message: The pool {id[1]} of file system {id[0]} has reached a normal level. |
| Description: The pool has reached a normal level. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| remote_exported_fs_unavail | STATE_CHANGE FAILED |
ERROR | no | Message: The remote file system {0} that is used for exports is not mounted. |
| Description: A remote file system that is used for export is not mounted. | ||||
| Cause: A remote file system for a declared export is not available. | ||||
| User Action: Check the remote mount states and exports of the remote cluster. | ||||
| stale_mount | STATE_CHANGE FAILED |
ERROR | no | Message: Found stale mounts for {0}. |
| Description: A mount state information mismatch was detected between the mmlsmount command and /proc/mounts. | ||||
| Cause: A file system may not be fully mounted or unmounted. | ||||
| User Action: To verify that all expected file systems are mounted, run the mmlsmount all_local -L command. | ||||
| unmounted_fs_check | STATE_CHANGE DEGRADED |
WARNING | no | Message: The file system {0} is probably needed, but not mounted. |
| Description: An internally mounted or a declared, but not mounted file system was detected. | ||||
| Cause: A declared file system is not mounted. | ||||
| User Action: To verify that all expected file systems are mounted, run the mmlsmount all_local -L command. | ||||
| unmounted_fs_ok | STATE_CHANGE HEALTHY |
INFO | no | Message: The file system {0} is probably needed, but not automounted or automount is prevented. |
| Description: An internally mounted or a declared but not mounted file system was detected. | ||||
| Cause: N/A | ||||
| User Action: N/A |