Dell PowerVault NX3610 User Manual - Page 88

Problematic SMB Access From A Linux Client, Strange UID And GID Numbers On Dell NAS System Files

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 88 highlights

Problematic SMB Access From A Linux Client Description Workaround A Linux/UNIX client is trying to mount a NAS cluster solution share using SMB (using /etc/fstab or directly using smbmount). A Linux/UNIX client is trying to access the file system using the smbclient command, such as: smbclient /// -U user %password -c ls It is recommended that you use the NFS protocol interfaces to access the NAS cluster solution FluidFS systems from Linux/UNIX clients. To workaround this issue: 1. Ensure that your admin creates NFS exports to same locations that you use to access using CIFS and connect to them using mount command from Linux/ UNIX clients. 2. Use NFS based interfaces to access the NAS cluster solution. For example, from the NAGIOS Linux management system, use the /check_disk command instead of the /check_disk_smb command. Strange UID And GID Numbers On Dell NAS System Files Description Cause Workaround New files created from Ubuntu 7.x clients get the UID and GID of 4294967294 (nfsnone). By default, Ubuntu 7.x nfs clients do not specify rpc credentials on their nfs calls. As a result, files created from these clients, by any user, are owned by 4294967294 (nfsnone) UID and GID. To force UNIX credentials on NFS calls, add the sec=sys option to the NAS cluster solution mounts in the Ubuntu fstab file. Troubleshooting Networking Issues Name Server Unresponsive Description Workaround All NIS, LDAP, or DNS servers are unreachable or not responding. For each server: 1. Ping the server from a client on NAS cluster solution subnet and verify it responds. 2. Issue a request to the server from a client on the NAS cluster solution subnet and verify it responds. 3. Check server logs to see what causes the server not to respond to requests. 88

  • 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
Problematic SMB Access From A Linux Client
Description
A Linux/UNIX client is trying to mount a NAS cluster
solution share using SMB (using /etc/fstab or directly
using smbmount).
A Linux/UNIX client is trying to access the file system
using the smbclient command, such as:
smbclient //<nas>/<share> -U user
%password -c ls
Workaround
It is recommended that you use the NFS protocol
interfaces to access the NAS cluster solution FluidFS
systems from Linux/UNIX clients. To workaround this
issue:
1. Ensure that your admin creates NFS exports to same
locations that you use to access using CIFS and
connect to them using mount command from Linux/
UNIX clients.
2. Use NFS based interfaces to access the NAS cluster
solution. For example, from the NAGIOS Linux
management system, use the
/check_disk
command instead of the
/check_disk_smb
command.
Strange UID And GID Numbers On Dell NAS System Files
Description
New files created from Ubuntu 7.
x
clients get the UID and
GID of 4294967294 (nfsnone).
Cause
By default, Ubuntu 7.
x
nfs clients do not specify rpc
credentials on their nfs calls. As a result, files created
from these clients, by any user, are owned by 4294967294
(nfsnone) UID and GID.
Workaround
To force UNIX credentials on NFS calls, add the
sec=sys
option to the NAS cluster solution mounts in the Ubuntu
fstab
file.
Troubleshooting Networking Issues
Name Server Unresponsive
Description
All NIS, LDAP, or DNS servers are unreachable or not
responding.
Workaround
For each server:
1. Ping the server from a client on NAS cluster solution
subnet and verify it responds.
2. Issue a request to the server from a client on the
NAS cluster solution subnet and verify it responds.
3. Check server logs to see what causes the server not
to respond to requests.
88