Share operation troubleshooting

Run command-line queries to troubleshoot errors when creating or mounting shares.

View error messages for shares
Copy link

You can use the command line to retrieve user support messages if a share shows an error status.

Procedure
Copy link

  1. When you create a share, run the following command to view the status of the share: 
    $ openstack share list
  2. If the status of your share shows an error, run the share message list command. You can use the --resource-id option to filter to the specific share you want to discover about: 
    $ openstack share message list [--resource-id]
  3. Check the User Message column in the share message list command output for a summary of the error.
  4. To view more details about the error, run the message show command, followed by the message ID from the message list command output: 
    $ openstack share message show <id>
    • Replace <id> with the message ID from the message list command output.

Debug share mount failures
Copy link

You can use these verification steps to identify the root cause of an error when you mount shares.

Procedure
Copy link

  1. Verify the access control list of the share to ensure that the rule that corresponds to your client is correct and has been successfully applied: 
    $ openstack share access list <share_01>
    • Replace <share_01> with either the share name or share ID.

      In a successful rule, the state attribute equals active.

  2. If the share type parameter is configured to driver_handles_share_servers=false, copy the hostname or IP address from the export location and ping it to confirm connectivity to the NAS server:

    Example:

    $ ping -c 1 198.51.100.13
PING 198.51.100.13 (198.51.100.13) 56(84) bytes of data.
64 bytes from 198.51.100.13: icmp_seq=1 ttl=64 time=0.048 ms--- 198.51.100.13 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.851/7.851/7.851/0.000 ms
  3. If you are using the NFS protocol, you can verify that the NFS server is ready to respond to NFS RPC calls on the correct port: 
    $ rpcinfo -T tcp -a 198.51.100.13.8.1 100003 4
program 100003 version 4 ready and waiting
    Note
    The IP address is in universal address format (uaddr), which adds two extra octets (8.1) to represent the NFS service port, 2049.

    If these verification steps fail, there might be a network connectivity issue or an issue with the back-end storage for the Shared File Systems service (manila). Collect the log files and contact Red Hat Support.