Bug 164241

Summary: mount doesn't support noacl option with nfs
Product: Red Hat Enterprise Linux 4 Reporter: Panu Matilainen <pmatilai>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-07-26 06:22:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Panu Matilainen 2005-07-26 06:20:20 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.0.4-1.4.1 Firefox/1.0.4

Description of problem:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/ref-guide/s1-nfs-client-config.html states "noacl  Turns off all ACL processing. This may be needed when interfacing with older versions of Red Hat Enterprise Linux, Red Hat Linux, or Solaris, since the most recent ACL technology is not compatible with older systems."

In RHEL 3 this used to work, except it was called no_acl, not noacl like the documentation says. In RHEL 4 it doesn't, and in certain environments the ACL's cause a significant slowdown (enormous amount of ACCESS operations)

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. mount -o noacl localhost:/some/path /mnt

  

Actual Results:  [root@lizilla ~]# mount -o noacl localhost:/tmp /mnt
Unsupported nfs mount option: noacl
[root@lizilla ~]# mount -o no_acl localhost:/tmp /mnt
Unsupported nfs mount option: no_acl


Expected Results:  It should have nfs-mounted the directory with ACL support off.

Additional info:
Comment 1 Panu Matilainen 2005-07-26 06:22:10 UTC 
Oops, sorry about the dupe...

*** This bug has been marked as a duplicate of 164240 ***