Administrator Guide

Workaround A possible way to verify this problem is to use newgrp to temporarily change the primary group of the
user and thus ensure it is passed to the server.
The simple workaround, although not always feasible, is to remove the user from unnecessary groups,
leaving only 16 groups or less.
Troubleshoot NAS File Access and Permissions Issues
This section contains probable causes of and solutions to common NAS le access and permissions problems.
Cannot Change the Ownership of a File or a Folder
Description Every le on the FluidFS cluster is owned by either a UNIX or NTFS user. Inability to change ownership is
treated dierently, depending on whether the access is native or non-native.
Cause The user is not authorized to perform the ownership change.
Workaround An authorized user must perform this action.
Cannot Modify NAS Files
Description A user or an application cannot modify a le.
Cause
The client cannot modify a le due to lack of permissions on the le.
The NAS volume has reached full capacity and the le system denies any write requests, including
overwrites.
The NAS volume is a target in a replication and is read-only.
Workaround
1. If the problem appears only on some les, this is a permission issue. Verify that the user account has
modify permissions on the le or use a dierent user account.
2. If the problem is related to a specic NAS volume, verify there is enough free space on the NAS
volume or expand it, and verify that the accessed NAS volume is not a target of a replication.
Mixed File Ownership Denied
Description
Both the le owner and group owner must be from the same identity type (UNIX vs. NTFS). An attempt
to set dierent identity types was detected.
Cause It is impossible to change only the le owner ID to UID if the original le ownership is SID/GSID.
Workaround To change the le 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 le 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 le 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.
656
FluidFS Troubleshooting