[LU-784] Cannot access named pipes or sockets with Posix-ACLs

• Type: Bug
• Resolution: Won't Fix
• Priority: Minor
• Affects Version/s: Lustre 1.8.6
• Environment: Tested on live systems with Lustre 1.8.5, RHEL4 and RHEL5 clients. Problem could be trivially reproduced in a VM running CentOS5 with Lustre 1.8.6-wc1.
• Severity: 3
• Assignee: Sarah Liu
• Reporter: Daniel Kobras (Inactive)

Description

Named pipes (FIFOs) and sockets in a Lustre filesystem can no longer be
accessed or unlinked if Posix-ACLs are set. This can be easily reproduced:

% mknod /lustre/test.pipe p
% setfacl -m g:testgroup:rx /lustre/test.pipe

Subsequently, all of the following operations result in EOPNOTSUPP, leaving an
inode that cannot be removed.

% stat /lustre/test.pipe
% unlink /lustre/test.pipe
% setfacl -b /lustre/test.pipe
% setfattr -x system.posix_acl_access testpipe
% getfacl /lustre/test.pipe
% getfattr -m '.*' /lustre/test.pipe

For each of these commands, syslog lists an error message like:

LustreError: 28069:0:(mdc_request.c:489:mdc_unpack_acl()) convert xattr to acl: -95

The ACLs on the test file work fine with getfacl when mounting the MDT as
ldiskfs, so they are stored correctly. Looking at mdc_unpack_acl() and
posix_acl_from_xattr(), the EOPNOTSUPP means they get garbled when they're
read back and sent to the client, though.

Issue Links

• duplicates: LU-2518 Corrupted files
• Trackbacks: Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA