Chapter 4. Distributed Hash Table Translator

Distributed Hash Table Translator Error Scenarios

109001

Description: A cached subvolume could not be found for the specified path.

Recommended Action: None.

109002

Description: A linkfile creation failed.

Recommended Action: None.

109003

Description: The value could not be set for the specified key in the dictionary.

Recommended Action: None.

109004

Description: Directory attributes could not be healed.

Recommended Action: None.

109005

Description: Self-heal failed for the specified directory.

Recommended Action:

1. Ensure that all the subvolumes are online and reachable.
2. Perform a lookup operation on the directory again.

109006

Description: The extended attributes could not be healed for the specified directory on the specified subvolume.

Recommended Action: None.

109007

Description: A lookup operation found a file with the same path on multiple subvolumes.

Note

If a rebalance process is in progress, this message can be ignored.

Recommended Action:

1. Create backups of the file on other subvolumes.
2. Inspect the content of all the files to identify and retain the most appropriate one.

109008

Description: A path resolves to a file on one subvolume and a directory on another.

Recommended Action:

1. Create a backup of the file with a different name and delete the original file.
2. In the newly created back up file, remove the trusted.gfid extended attribute using the command:
   setfattr -x trusted.gfid <path to the newly created backup file>
3. Perform a new lookup operation on both the new and old paths.
4. From the mount point, inspect both the paths and retain the relevant file or directory.

109009

Description: The GFID of the file or directory is different on different subvolumes.

Recommended Action: None.

109010

Description: The GFID of the specified file or directory is NULL.

Recommended Action: None.

109011

Description: The hashed subvolume could not be found for the specified file or directory.

Recommended Action: None.

109012

Description: The Distributed Hash Table Translator could not be initiated as the system is out of memory.

Recommended Action: None.

109013

Description: Invalid Distributed Hash Table configuration in the volume configuration file.

Recommended Action: None.

109014

Description: Invalid disk layout.

Recommended Action: None.

109015

Description: Invalid Distributed Hash Table configuration option.

Recommended Action:

1. Reset the option with a valid value using the gluster volume set <VOLNAME> command.
2. Restart the process that logged the message in the log file.

109016

Description: The fix layout operation failed.

Recommended Action: None.

109017

Description: Layout merge failed.

Recommended Action: None.

109018

Description:The layout for the specified directory does not match that on the disk.

Recommended Action: None.

109019

Description:No layout is present for the specified file or directory.

Recommended Action: None.

109020

Description:Informational message: Migration of data from the cached subvolume to the hashed subvolume is complete.

Recommended Action: None.

109021

Description:Migration of data failed during the rebalance operation.

Cause:Directories could not be read to identify the files for the migration process.

Recommended Action:The log message indicates the reason for the failure and the corrective action depends on the specific error that is encountered. The error would be one of the standard UNIX errors.

109022

Description:Informational message: The file was migrated successfully during the rebalance operation.

Recommended Action:None.

109023

Description:File migration failed during the rebalance operation.

Cause:Rebalance moves data from the cached subvolume to the hashed subvolume. Migrating a single file is a multi-step operation which involves opening, reading, and writing the data and metadata. Any failures in this multi-step operation can result in a file migration failure.

Recommended Action:The log message would indicate the reason for the failure and the corrective action depends on the specific error that is encountered. The error is one of the standard UNIX errors.

109024

Description:The system is out of memory.

Recommended Action:None.

109025

Description:The opendir() call failed on the specified directory.

Cause:When a directory is renamed, the DHT Translator checks whether the destination directory is empty. This message indicates that the opendir() call on the destination directory has failed.

Recommended Action:The log message indicates the reason for the failure and the corrective action depends on the specific error that is encountered. The error is one of the standard UNIX errors.

109026

Description:The rebalance operation failed.

Possible Cause:A subvolume is down.

Recommended Action:Restart the rebalance operation after all the subvolumes are online.

109027

Description:Failed to start the rebalance process.

Recommended Action:Identify the reason for failure in the log files.

109028

Description:Informational Message: Indicates the status of the rebalance operation and details such as the number of files migrated, skipped, or failed.

Recommended Action:None.

109029

Description:The rebalance operation was aborted by the user.

Recommended Action:None.

109030

Description:The file or directory could not be renamed.

Recommended Action:Ensure that all the subvolumes are reachable and try renaming the file or directory again.

109031

Description:Attributes could not be set for the specified file or directory.

Recommended Action:None.

109032

Description:The specified subvolume is running out of file system inodes. If all subvolumes run out of inodes, then new files cannot be created.

Recommended Action:Add more nodes to the cluster if all subvolumes run out of inodes.

109033

Description:The specified subvolume is running out of disk space. If all subvolumes run out of space, new files cannot be created.

Recommended Action:Add more nodes to the cluster if all subvolumes run out of disk space.

109034

Description:Failed to unlink the specified file or directory.

Recommended Action:The log message indicates the reason for the failure and the corrective action depends on the specific error that is encountered.

109035

Description:The layout information could not be set in the inode.

Recommended Action:None.