Errors encountered with filesets

The analysis of those errors, which might be encountered while dealing with the filesets.

Following errors might be encountered with filesets:
  1. Problems can arise when running backup and archive utilities against a file system with unlinked filesets. See the Filesets and backup topic in the IBM Storage Scale: Administration Guide for details.
  2. In a rare case, if the mmfsck command encounters a serious error that is checking the file system's fileset metadata, it might not be possible to reconstruct the fileset name and comment. These cannot be inferred from information elsewhere in the file system. If this happens, then the mmfsck command creates a dummy name for the fileset, such as Fileset911 and the comment is set to the empty string.
  3. Sometimes the mmfsck command encounters orphaned files or directories (those without a parent directory), and traditionally these are reattached in a special directory that is called lost+found in the file system root. However, when a file system contains multiple filesets orphaned files and directories are reattached in the lost+found directory in the root of the fileset to which they belong. For the root fileset, this directory appears in the usual place, but other filesets might each have their own lost+found directory.

Active file management fileset errors

When the mmafmctl Device getstate command displays a NeedsResync target or fileset state, inconsistencies exist between the home and cache. To ensure that the cached data is synchronized with the home and the fileset is returned to Active state, either the file system must be unmounted and mounted, or the fileset must be unlinked and linked. Once this is done, the next update to fileset data triggers an automatic synchronization of data from the cache to the home.