[LU-1790] permission denied error on the client

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.1.2
• Type: Bug
• Priority: Major
• Reporter: Mi Zhou
• Assignee: WC Triage
• Resolution: Not a Bug

Environment

CentOS6.1 on server
CentOS5.6 on client

• Severity: 2

Description

On a client, we found only root can write to the Lustre volume, any other user get a "permission denied". We use NIS on the client and the MDS. We have enabled ACL on the MDS. And from client, it shows "acl" when we do this:
[root@nodem57 scratch]# lctl get_param n mdc.scratch-MDT0000-mdc*.connect_flags | grep acl
acl

On a client:
[mzhou@nodem57 scratch]$ ls -l
ls: nodem57: Permission denied
total 8
drwxr-xr-x 4 root root 4096 Aug 23 14:34 nodem57
drwxrwxrwx+ 2 root root 4096 Aug 24 11:08 test
[mzhou@nodem57 scratch]$ cd test
[mzhou@nodem57 test]$ ls
ls: .: Permission denied

Here is the from /var/log/message on the client.

Aug 27 11:56:28 nodem57 kernel: LustreError: 23079:0:(mdc_locks.c:723:mdc_enqueue()) ldlm_cli_enqueue: -13
Aug 27 11:56:28 nodem57 kernel: LustreError: 23079:0:(file.c:2196:ll_inode_revalidate_fini()) failure -13 inode 523777
Aug 27 11:56:28 nodem57 kernel: LustreError: 23079:0:(mdc_locks.c:723:mdc_enqueue()) ldlm_cli_enqueue: -13
Aug 27 11:56:28 nodem57 kernel: LustreError: 23079:0:(file.c:2196:ll_inode_revalidate_fini()) failure -13 inode 523777
Aug 27 12:03:31 nodem57 kernel: LustreError: 23261:0:(mdc_locks.c:723:mdc_enqueue()) ldlm_cli_enqueue: -13
Aug 27 12:03:31 nodem57 kernel: LustreError: 23261:0:(mdc_locks.c:723:mdc_enqueue()) Skipped 2 previous similar messages
Aug 27 12:03:31 nodem57 kernel: LustreError: 23261:0:(file.c:2196:ll_inode_revalidate_fini()) failure -13 inode 523777
Aug 27 12:03:31 nodem57 kernel: LustreError: 23261:0:(file.c:2196:ll_inode_revalidate_fini()) Skipped 2 previous similar messages

Comments

[Cliff White (Inactive)]

This issue is not related to ACLs, are the user permissions correct when not using Lustre? If the user information is correct on the MDS, permissions should work, so verify that NIS is looking up the user properly on the MDS.

[Mi Zhou]

Hi,

It can be closed. NIS on mds was misconfigured, fiexed that and the error is gone.

Thanks,

Mi