User's Manual

204 Troubleshooting
HSM file system mounting problems
Description On a Linux FSE system with an entry in the /etc/fstab file for the /fse/fsefs_01 file system with
type hsmfs, running the mount /fse/fsefs_01 command produces the following error:
# mount /fse/fsefs_01/
mount: wrong fs type, bad option, bad superblock on
/dev/vg_fse/fsefs_01, or too many mounted file systems
(Linux system-specific)
Explanation This error is reported if any of the following is true:
• FSE daemons are not running.
• There is no FSE partition configured for the specified HSM file system or logical volume.
•The Major:Minor parameter in the FSE partition configuration is incorrect.
Workaround Determine the cause of this error and act accordingly:
• Check if FSE is running using the fse --status command; if needed, start the FSE
services using the fse --start command.
• Check if the partition for the mount point is configured in the FSE implementation.
The logical volume is configured with its Major:Minor parameter specified in the FSE
partition configuration file. You need to verify this parameter matches the actual
Major:Minor parameter assigned to the logical volume (file system). For this purpose, run the
following commands and compare their outputs; the retrieved Major:Minor parameters
should be the same:
# fsepartition --show PART_01 | grep FileSystemID | sed \
's/FileSystemID = \"\(.*\)"/\1/'
# ll /dev/vg_fse/fsefs_01 | awk '{print $5 $6}'
If the numbers displayed are not the same for both commands, see the FSE Installation Guide
for information on proper logical volume and partition configuration.
Debugging HSM file system filter may also help solving the problem. For details, see
”Debugging HSM file system filter” on page 229.
Description On a Windows FSE system, while running the fse --mount command to mount an HSM file
system, the command may fail and will report an error (Windows-system specific).
Explanation There are two possible causes for this problem:
• Cause 1: NTFS has already attached to the disk volume that stores the HSM file system, and
the HSM file system filter cannot gain control over it. This is the most probable cause for the
described problem.
• Cause 2: The mount point directory for the HSM file system is not empty. This is a less
probable cause.
Workaround According to the determined cause, proceed as follows:
• Cause 1: Run the following command to detach NTFS and then retry mounting the HSM file
system:
C:\>fse --dismount-ntfs VolumeName
• Cause 2: Delete the directory contents and try to mount the file system again.