V11 SP8
Loading...

3DFS FAQs

Why do I get an I/O error when trying to access files?

The 3DFS server is not able to either browse a directory or to restore a file on the NFS client. Check the 3dnfs.log on the 3DFS server and the .3dfs file in the 3DFS cache folder:

Note: Do not modify the 3dnfs.log file or the .3dfs file.

[root@3dfsSelCacheServer 3dfs]# pwd
/opt/commvault/iDataAgent/jobResults/3dfs
[root@3dfsSelCacheServer 3dfs]# ls -ltr
drwxrwxrwx. 3 root root 4096 Dec 15 11:40 CM
-rw-rw-rw-. 1 root root 0 Dec 15 12:02 mounted
drwxrwxrwx. 4 root root 4096 Dec 15 14:08 CLIENT_PATHS
drwxrwxrwx. 6 root root 4096 Dec 15 14:41 AF_PATHS
-rw-rw-rw-. 1 root root 95 Dec 15 14:41 exports
-rw-rw-rw-. 1 root root 108 Dec 15 14:41 clinfoids
-rw-rw-rw-. 1 root root 96 Dec 15 14:41 accesspaths

CLIENT_PATHS contains a folder for each item in the backup that is browsed or restored until that time. The same folder has the .3dfs file, which contains the path in AF_PATHS. This path has the data file that contains the file content that is being restored or modified.

On CIFS clients, verify the following:

  • NFS-Ganesha might have stopped responding. CIFS share support is dependent on NFS-Ganesha for all operations. Check if ganesha.nfsd service is running on the ps command output.
  • If you get the File is inaccessible error, NFS-Ganesha might have stopped responding and restarted. Without closing the window, connect to the CIFS share again by clicking \\3dnfs_share_path.
  • Check if the same file is accessible from s3dfsRootDir/exports/share_name/file_name which is the locally mounted NFS export for the corresponding CIFS share.

The export command returns an error

  • Check all the parameters given to this command.
  • Check the connectivity between the machine where the QCommand is executed (the CommServe computer) and the 3DFS server (MediaAgent).
  • Check the 3dnfs.log for a new configuration remote procedure call (RPC) to export the share.
  • By default, 3DFS allows you to export 5 NFS shares. Increase the number of NFS shares that you can export by using the n3dfsMaxExports additional setting.

The unexport command returns an error

  • Check all the parameters given to this command. The share name must be the name that is given by the corresponding export command.
  • Check the connectivity between the machine where the QCommand is being executed (the CommServe computer) and the 3DFS server (the MediaAgent).
  • Check the 3dnfs.log for a new configuration remote procedure call (RPC) to unexport the share.

The mount command fails

  • Check if 3DFS is up and running using the commvault list command.
  • Check if you exported the share for this machine (using the export command).
  • Check if the 3DFS server is reachable from the NFS client.
  • Check if the NFS client’s IP address is given in the list of IP addresses or host names in the export command.
  • Check the 3dnfs.log for any other issue.
  • For CIFS shares, check if the net conf listshares command on the 3DFS server shows the CIFS share that you are trying to connect.

The unmount command fails

Check if the mounted path is in use.

Browsing a folder or copying a file fails

  • Check if the share is still exported. Probably, you did not unmount it, but unexported it.
  • Check all the points given in the Mount Command Fails section.

CIFS shares are visible after unexporting 

The Windows client computer might be actively using the share when you unexported the share. Disconnect and reconnect to the 3DFS server by removing all cached sessions.

Permission denied error for the  CIFS share

  • Check if the list of hosts allowed to access the CIFS share has your client IP address by running the net conf listshares command followed by the net conf showshare share_name command.
  • Check if the credentials provided for authentication on the Windows Server are correct. Check /var/log/commvault/Log_files/log.smbd for more details.
  • If you are providing credentials of domain B while your 3DFS server is part of domain A, check if the required Active Directory Trust relationships are present for the authentication to succeed.