Dell PowerVault NX3610 User Manual - Page 77

NFS Export Does Not Exist, NFS File Access Denied, export is available to this client

Page 77 highlights

NFS Export Does Not Exist Description Cause Workaround NFS File Access Denied Description Cause Workaround • Check the network connection by trying to NFS mount from some other system. • Verify if other users experience the same problem. If the appliance is not responding due to the program not registered, check if the port mapper on your client is up. If the issue is due to access denied: • Get a list of the appliance exported file systems using the command: showmount -e • Check the system name or netgroup name is not in the user list for the file system. • Check the file systems related to the NFS through the NAS cluster solution user interface. If the issue is due to the directory, check the spelling in your command and try to run the mount command on both directories. Attempted to mount an export that does not exist. This failure is commonly caused by spelling mistakes on the client system or when accessing the wrong server. 1. Check the available exports on the NAS; verify that all the required exports exist. 2. On the problematic client, verify that the relevant export is available to this client: 3. % showmount -e 4. Export list for : 5. /abc 10.10.10.0 6. /xyz 10.10.10.0 7. If the export is available, review the export name spelling in the relevant mount command on the client. It is recommended to copy paste the export name from the showmount output to the mount command. This event is issued when an NFS user does not have enough permissions for the file on a NAS container. File ownership is UID/UNIX and the user is not privileged to access the file, or, file ownership is SID/ACL and after translation to UID/UNIX the permissions do not allow access to the file. For native access (when CIFS user accesses SID/ACL file or NFS user accesses UID/UNIX file) understanding the missing permission is standard. 77

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117

Check the network connection by trying to NFS
mount from some other system.
Verify if other users experience the same problem.
If the appliance is not responding due to the program not
registered, check if the port mapper on your client is up.
If the issue is due to access denied:
Get a list of the appliance exported file systems
using the command:
showmount -e <FluidFS hostname>
Check the system name or netgroup name is not in
the user list for the file system.
Check the file systems related to the NFS through
the NAS cluster solution user interface.
If the issue is due to the directory, check the spelling in
your command and try to run the mount command on both
directories.
NFS Export Does Not Exist
Description
Attempted to mount an export that does not exist.
Cause
This failure is commonly caused by spelling mistakes on
the client system or when accessing the wrong server.
Workaround
1. Check the available exports on the NAS; verify that
all the required exports exist.
2. On the problematic client, verify that the relevant
export is available to this client:
3.
% showmount -e <Server name/IP>
4.
Export list for <Server name/IP>:
5.
/abc 10.10.10.0
6.
/xyz 10.10.10.0
7. If the export is available, review the export name
spelling in the relevant mount command on the
client. It is recommended to copy paste the export
name from the showmount output to the mount
command.
NFS File Access Denied
Description
This event is issued when an NFS user does not have
enough permissions for the file on a NAS container.
Cause
File ownership is UID/UNIX and the user is not privileged
to access the file, or, file ownership is SID/ACL and after
translation to UID/UNIX the permissions do not allow
access to the file.
Workaround
For native access (when CIFS user accesses SID/ACL file
or NFS user accesses UID/UNIX file) understanding the
missing permission is standard.
77