Dell PowerVault NX3610 User Manual - Page 79

NFS Mount Path Does Not Exist, restore is complete.

Get Dell PowerVault NX3610 PDF manuals and user guides View all Dell PowerVault NX3610 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 79 highlights

Workaround NFS Mount Path Does Not Exist Description Cause Workaround Repeat the below process for each configured NIS server, each time leaving just a single NIS used, starting with the problematic NIS server. 1. Inspect the NIS/LDAP server logs and see if the reason for the error is reported in the logs. 2. Network test: 3. Try pinging the NAS from a client located in the same subnet as the NIS/LDAP server. 4. Try pinging the NIS/LDAP server from a client located in the same subnet as the NAS. 5. If a packet loss is evident on one of the above, resolve the network issues in the environment. 6. Using a Linux client located in the same subnet as the NAS and configured to use the same directory server, query the netgroup details from the NIS/ LDAP server using the relevant commands. Ensure that the reply is received in a timely manner (up to 3 seconds). You can temporarily workaround the problem by removing the netgroup restriction on the export and/or by defining an alternative directory server. Identify the relevant export and the options defined for it, while focusing on the netgroup definition. Document the used netgroup in order to restore it once the issue is solved and remove the netgroup limitation. Client tries to mount a mount path that does not exists on a NAS container. This error usually occurs in one of the following scenarios: • When accessing a system which is being restored from backup or remote replication. The full directory structure is available only when the restore is complete. • When a client with an authorization to access a higher directory in the same path deletes or alters a directory which is being mounted by another client. • When multiple users are accessing the same data set, it is recommended to apply a strict permission scheme to avoid this scenario. 1. If the NAS system is being restored, communicate the current status to the client and instruct the client to wait for the restore process to complete. 2. In the other case, there are three options: a. Restore the problematic path from a backup. b. Manually create the missing directories to enable the mount. Clients receive errors when trying to access existing data in a deleted path. 79

  • 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
Workaround
Repeat the below process for each configured NIS server,
each time leaving just a single NIS used, starting with the
problematic NIS server.
1. Inspect the NIS/LDAP server logs and see if the
reason for the error is reported in the logs.
2. Network test:
3. Try pinging the NAS from a client located in the
same subnet as the NIS/LDAP server.
4. Try pinging the NIS/LDAP server from a client
located in the same subnet as the NAS.
5. If a packet loss is evident on one of the above,
resolve the network issues in the environment.
6. Using a Linux client located in the same subnet as
the NAS and configured to use the same directory
server, query the netgroup details from the NIS/
LDAP server using the relevant commands. Ensure
that the reply is received in a timely manner (up to 3
seconds).
You can temporarily workaround the problem by removing
the netgroup restriction on the export and/or by defining
an alternative directory server.
Identify the relevant export and the options defined for it,
while focusing on the netgroup definition. Document the
used netgroup in order to restore it once the issue is
solved and remove the netgroup limitation.
NFS Mount Path Does Not Exist
Description
Client tries to mount a mount path that does not exists on a
NAS container.
Cause
This error usually occurs in one of the following scenarios:
•
When accessing a system which is being restored
from backup or remote replication. The full
directory structure is available only when the
restore is complete.
•
When a client with an authorization to access a
higher directory in the same path deletes or alters
a directory which is being mounted by another
client.
•
When multiple users are accessing the same data
set, it is recommended to apply a strict permission
scheme to avoid this scenario.
Workaround
1. If the NAS system is being restored, communicate
the current status to the client and instruct the client
to wait for the restore process to complete.
2. In the other case, there are three options:
a. Restore the problematic path from a backup.
b. Manually create the missing directories to
enable the mount. Clients receive errors when
trying to access existing data in a deleted path.
79