Chapter 2 NAS Head 2-65
3. Type the administrator password to access the administration interface.
4. Navigate to System Operations/Assign Language. Select the desired language, and
click the “Apply” button.
GID for new NFS objects is incorrect.
StorEdge doesn’t recognize the set GID bit.
The StorEdge software supports three ways of setting the group ID of new files and
directories. The default is to inherit GID from the parent directory in all cases. This
behavior is configurable only at the Command Line Interface (CLI).
1. To access the StorEdge CLI, connect to the StorEdge via Telnet, and type “admin”
at the [menu] prompt and enter the administrator password.
2. At the CLI, enter “fsctl gidmode <type>”. <Type> is one of the following:
■ bsdInherit the group id from the parent directory
■ sysvApply the creating user's primary group id
■ sgidSet the group id according to the set GID bit (02000) in the parent directory
mode.
For sgid, when the set GID (S_ISGID) bit is set, both the group ID and the set GID bit
will be inherited from the parent directory. Otherwise, the creating user's group ID is
applied.
Chown by root fails if it would put target user over hard quota.
This behavior is by design. StorEdge does not allow users to exceed their hard quota.
The solution is to modify the quota either temporarily or permanent.
NFS User can’t access his own files created with CIFS/SMB
account.
This is an indication that there is a problem with user or group mapping. From an
NFS mount, use ls –ln to determine the current ownership of the file. If the owner’s
UID or GID is not what is expected, proceed according to the instructions in the
Troubleshooting Guide: “Windows users are not mapped to the expected NFS
group.” or “User maps are incorrect.”