Possible Cause: The user might not be a trustee of the file or might not have sufficient rights.
Action: Add the user as a trustee and provide sufficient rights to the file.
Possible Cause: The user might not have sufficient UNIX permissions.
Action: Complete the following steps:
Identify the user's UID/GID in his or her UNIX profile in eDirectory.
If the UNIX profile for the user does not exist, create it.
Identify whether the user's UNIX access is coming from user, group, or other permissions.
Grant the read/write permission to the appropriate entity (user, group, or other).
Possible Cause: The volume might have been mounted as read-only.
Action: Dismount and remount the volume with read-write mode using gyumount.nlm and gymount.nlm..
Possible Cause: The path might have been shared as read-only from the NFS server.
Action: Reshare the path as read-write and dismount and remount the volume using gyumount.nlm and gymount.nlm.
Possible Cause: The user's UNIX profile might be set with UID = 0.
Action: Verify for root access by entering the gymount -d -volparams command at the system console prompt.
If root access is not given, make sure that the world/other group has the read right.
Possible Cause: The file might be a special file such as block device, character device, or symbolic links file.
Problem: If the file is a special file, then it is not possible to either open it or read its contents.