User's Manual

hp StorageWorks File System Extender User Guide 205
Description Output of the command fsepartition --list shows a partition as ‘ready’ or ‘mounted’ but the
belonging HSM file systems cannot be accessed (Linux system-specific).
Explanation Regardless of the operating system, the output of the fsepartition --list command
shows the status of the corresponding fse-pm and fse-hsm processes, and not the status of
the corresponding HSM file system. If the fse-pm process is running, the status is ready. If the
fse-hsm process is running, the status is mounted. However, the fse-hsm process should
normally be running only when the HSM file system is mounted.
To see the detailed status of the partition and its corresponding HSM file system, use the
following command:
fsepartition --status PartitionName
Workaround If the file system is not mounted, you can mount it manually using the following command. The
command requires that the HSM file system has an appropriate entry in the /etc/fstab file:
# mount /fse/fsefs_01
For details, see ”Mounting HSM file systems on Linux platform” on page 73.
Description Output of the command fsepartition --list shows a partition as ‘ready’ or ‘mounted’ but the
belonging HSM file systems cannot be accessed (Windows-system specific).
Explanation Further inspection may indicate the following causes for the problem:
• Cause 1: The HSM file system is mounted, but the Hierarchical Storage Manager is not
running.
• Cause 2: fse.log reports that no HSM file system is ready for host FSEClientName on
the respective FSE server.
• Cause 3: fse.log reports that a volume is configured, but no mount point is defined.
Workaround According to the determined cause, proceed as follows:
• Cause 1: Check that the state of the FSE partition on the FSE server is ready (and not
disabled or stopped) using the command:
C:\>fsepartition --status PartitionName
• Cause 2: Perform the following steps:
• Check that client host is accessible from the FSE server with the same fully-qualified
domain name as it is accessible locally.
•Check the DNS suffix:
On the Windows desktop, right-click My Computer, then click Properties and select
Network Identification.
Click Properties, and then click More and enter the suffix.
• Cause 3: When such a warning is reported and the mountvol command shows the line
*** NO MOUNT POINTS *** for that volume, proceed as follows:
• In case you have not yet defined the mount point, define the mount point with the
command fse --mount command. For details, see ”Configuring a regular FSE
partition on Windows platform” on page 70.
• If you have already defined the mount point, check its VolumeName, written in the
%InstallPath%\var\log\fse.log. Verify that the VolumeName, written in the
FSE partition configuration file on the FSE server, which you specified before installing a
Windows client, matches the volume name of the configured FSE volume on the
respective client. For more information on required VolumeName format, see
”Configuring a regular FSE partition on Windows platform” on page 70.