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.

On SMB clients, verify the following:

NFS-Ganesha might have stopped responding. SMB 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 SMB 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 SMB share.

The export command returns an error

Check all the parameters given to this command.
Check the connectivity between the CommServe computer and the 3DFS server (MediaAgent).
Check the 3dnfs.log for a new configuration remote procedure call (RPC) to export the share.
If share creation fails, check EvMgrS.log on the CommServe computer, and CVD.log on the 3DFS server.

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 CommServe computer and the 3DFS server (MediaAgent).
Check the 3dnfs.log for a new configuration remote procedure call (RPC) to unexport the share.
If share creation fails, check EvMgrS.log on the CommServe computer, and CVD.log on the 3DFS server.

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 SMB shares, check if the net conf listshares command on the 3DFS server shows the SMB 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.

SMB 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.

Check if the list of hosts allowed to access the SMB 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.

The following sequence causes stale entries of Samba (SMB) share to be displayed on Samba clients:

Create an ObjectStore with SMB support enabled.
Disable SMB support and restart the 3DFS service.
Delete the ObjectStore.

SMB shares are not visible because the Samba server is not started by 3DFS.
Enable SMB support and restart the 3DFS service.

The stale entries of Samba share for the ObjectStore deleted in step 3 will be displayed.

For the most recent backup data to appear in the exported share, the software needs a refresh time of 60 seconds.