Skip to Main Content
Forums

Hardware

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Recovering From a Hung mount Command

If the mount(1M) command hangs, follow the procedure in this page. You have a hung mount(1M) command if, for example, the mount(1M) command fails with a connection error or with a Server not responding message that does not resolve itself within 30 seconds.

The most typical remedy for a hung mount(1M) command is presented first. If that does not work, perform the subsequent procedures.

To Verify Network Connections

The netstat(1M) command verifies that the sam-sharefsd daemon’s network connections are correctly configured.

  1. Become superuser on the metadata server.
  2. Type the samu(1M) command to invoke the samu(1M) operator utility.

    For example:
    # samu

  • Press :P to access the Active Services display.

    The following code example shows a P display.

    Active Services samu 4.4 09:02:22 Sept 22 2005Registered services for host `titan': sharedfs.sharefs1 1 service registered.

    Examine the output. In the above code example, look for a line that contains sharedfs.filesystem-name. In this example, the line must contain sharedfs.sharefs1.

    If no such line appears, you need to verify that both the sam-fsd and sam-sharefsd daemons have started. Perform the following steps:
    1. Enable daemon tracing in the defaults.conf file.

      For information about how to enable tracing, see defaults.conf(4) or see Step 2 in To Examine the sam-sharefsd Trace Log.
    2. Examine your configuration files, especially /etc/opt/SUNWsamfs/mcf.
    3. After you have checked your configuration files and verified that the daemons are active, begin this procedure again.
  • Enter the samsharefs(1M) command to check the hosts file.

    The following code example shows the samsharefs(1M) command and correct output.

    titan-server# samsharefs -R sharefs1 # # Host file for family set `sharefs1' # # Version: 3 Generation: 50 Count: 4# Server = host 0/titan, length = 216# titan 173.26.2.129 1 - server tethys 173.26.2.130 2 - dione dione 0 - mimas mimas 0 -

    In the output on your system, verify the following:
    • The host name is present in column 1 of the output and it is designated as the server.
    • The host IP address is present in column 2. If there are multiple IP addresses, make sure that they are all valid.
  • Enter the netstat(1M) command on the server.

    The following code example shows the netstat(1M) command entered on server titan.

    titan-server# netstat -a | grep sam-qfs *.sam-qfs *.* 0 0 24576 0 LISTEN *.sam-qfs *.* 0 0 24576 0 LISTEN titan.32834 titan.sam-qfs 32768 0 32768 0 ESTABLISHED titan.sam-qfs titan.32891 32768 0 32768 0 ESTABLISHED titan.sam-qfs tethys.32884 24820 0 24820 0 ESTABLISHED titan.sam-qfs dione.35299 24820 0 24820 0 ESTABLISHED *.sam-qfs *.* 0 0 24576 0 LISTEN

    Verify that the output from the netstat(1M) command on the server contains the following:
    • Three LISTEN entries.
    • Two ESTABLISHED entries for the host.
    • One ESTABLISHED entry for each client that is configured and running the sam-fsd daemon.
      This example shows ESTABLISHED entries for tethys and dione. There should be one ESTABLISHED entry for each client that is configured and running, whether or not it is mounted.
  • Enter the netstat(1M) command on the client.

    The following code example shows the netstat(1M) command entered on client dione.

    titan-server# netstat -a | grep sam-qfs *.sam-qfs *.* 0 0 24576 0 LISTEN *.sam-qfs *.* 0 0 24576 0 LISTEN titan.32834 titan.sam-qfs 32768 0 32768 0 ESTABLISHED titan.sam-qfs titan.32891 32768 0 32768 0 ESTABLISHED titan.sam-qfs tethys.32884 24820 0 24820 0 ESTABLISHED titan.sam-qfs dione.35299 24820 0 24820 0 ESTABLISHED *.sam-qfs *.* 0 0 24576 0 LISTEN

  • Verify that the output contains the following:
    • Three LISTEN entries. All entries are for the sam-fsd daemon.
    • One ESTABLISHED entry.

      If these lines are present, then the network connection is established.

      If an ESTABLISHED connection is not reported, perform one or more of the following procedures:

To Verify That the Client Can Reach the Server

Perform these steps if using the procedure described in To Verify Network Connections did not show an ESTABLISHED connection.

  1. Use the samsharefs(1M) command to verify the hosts file on the server.

    You can issue the samsharefs(1M) command on alternate server hosts and client hosts that have no nodev devices listed in the host’s mcf(4) entry for the file system. For this step, use this command in the following format:

    samsharefs -R <filesystem>

    For filesystem, specify the name of the Oracle's Sun StorageTek QFS shared file system as specified in the mcf file. The following code example shows the samsharefs(1M) -R command.

    titan-server# samsharefs -R sharefs1 # # Host file for family set `sharefs1' # # Version: 3 Generation: 50 Count: 4# Server = host 0
    Comments
    Post Details
    Added on Jun 22 2015
    #legacy-documents, #oracle-hsm, #server-storage-systems, #systems-configuration-support, #troubleshooting
    0 comments
    289 views