Bug 962450
Summary: | POSIX ACLs fail display / apply / set on NFSv3 mounted Gluster filesystems | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | James Yale <james.yale> |
Component: | nfs | Assignee: | bugs <bugs> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0-beta | CC: | bugs, ctn, gluster-bugs, james.yale, skoduri, vagarwal, yoyoprs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-07 14:05:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Yale
2013-05-13 14:14:55 UTC
On debian based, the problem is reversed on 3.4 stable. On Nfs3(mounted with acl) we can see the acl on files, and via gluster fuse client : acl on files do not appear. This is also the case with the release version in the yum repository for CentOS. It works properly with FUSE, does not work with NFSv3. [root@node003 ~]# rpm -qa | grep gluster glusterfs-libs-3.4.0-8.el6.x86_64 glusterfs-server-3.4.0-8.el6.x86_64 glusterfs-3.4.0-8.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 glusterfs-fuse-3.4.0-8.el6.x86_64 [root@node003 ~]# [root@node003 ~]# mount -t nfs -o vers=3,acl,tcp,noatime node000:/test-data /mnt/test-data-nfs [ctn@node003 test-data-nfs]$ getfacl * getfacl: original: Invalid argument getfacl: testing: Invalid argument [ctn@node003 test-data-nfs]$ ls original/ testing/ [ctn@node003 test-data-nfs]$ getfacl * getfacl: original: Invalid argument getfacl: testing: Invalid argument Can you please confirm it on the latest GlusterFS mainline release? Can you please confirm it on the latest GlusterFS mainline release? GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed. GlusterFS 3.4.x has reached end-of-life. If this bug still exists in a later release please reopen this and change the version or open a new bug. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |