Administrator Guide

Table Of Contents
Cause It is impossible to change only the file owner ID to UID if the original file ownership is SID/GSID.
Workaround To change the file ownership to UNIX style ownership, set UID and GID at same time.
Problematic SMB Access From a UNIX/Linux Client
Description A UNIX/Linux client is trying to mount a FluidFS cluster SMB share using SMB (using /etc/fstab
or directly using smbmount).
Cause A UNIX/Linux client is trying to access the file system using the smbclient command, for example:
smbclient //<FluidFS_cluster_name>/<SMB_share> -U user%password -c ls
Workaround It is recommended that you use the NFS protocol interfaces to access the FluidFS cluster file system
from UNIX/Linux clients. To work around this issue:
1. Ensure that the administrator creates NFS exports to the same locations that you use to access
using SMB and connect to them using the mount command from UNIX/Linux clients.
2. Use NFS-based interfaces to access the FluidFS cluster. 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 FluidFS cluster mounts in the
Ubuntu fstab file.
Troubleshoot Networking Problems
This section contains probable causes of and solutions to common networking problems.
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 the FluidFS cluster subnet and verify that it responds.
2. Issue a request to the server from a client on the FluidFS cluster subnet and verify that it
responds.
3. Check the server logs to see what is causing the server not to respond to requests.
Troubleshooting DNS Configurations
Description
Clients are unable to connect to the FluidFS cluster using the system name and/or unable to resolve
host names.
Cause Probable causes might be:
Client IP address information is not set correctly.
The FluidFS cluster is not configured to use the correct DNS server.
DNS records are incorrect.
Workaround 1. Verify that the client IP address information is set correctly.
2. Verify that the FluidFS cluster is configured to use the correct DNS server.
3. Contact the DNS server administrator to verify the DNS record creation.
FluidFS Administration 489