User's Manual

HP StorageWorks File System Extender Software user guide 255
HSM file system mounting problems
Description On a system, where the /etc/fstab file contains an entry 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 device file specified for the variable FileSystemID 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
processes 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 FileSystemID variable specified in the FSE partition
configuration file. You need to verify its value matches the actual device file assigned to the
logical volume (file system). For this purpose, first determine the mapped directory:
#ls -l /dev/
VG_fse/fsefs_01
rwxrwxrwx 1 root root 25 May 18 11:55 /dev/vg_fse/fsefs_01 ->
/dev/mapper/vg_fse-fsefs_01
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/mapper/vg_fse-fsefs_01 | awk '{print $5 $6}'
If the numbers displayed are not the same for both commands, you need to properly
reconfigure the FSE partition. For details, see the FSE installation guide for Linux.
Debugging HSM file system filter may also help solving the problem. For details, see
”Debugging HSM file system filter” on page 281.