Bug 858426 - Mounting bricks with "-o acl" should not be needed
Summary: Mounting bricks with "-o acl" should not be needed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Administration_Guide
Version: 2.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Divya
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 840489
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-18 22:21 UTC by Scott Haines
Modified: 2015-04-10 07:16 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 840489
Environment:
Last Closed: 2015-04-10 07:16:13 UTC
Embargoed:


Attachments (Terms of Use)

Description Scott Haines 2012-09-18 22:21:03 UTC
+++ This bug was initially created as a clone of Bug #840489 +++

9.5.7.1 on page 51 explicitly mentions re-mounting the bricks with "-o acl", but for XFS (and most filesystems) that is the default. It is probably more common to need to remount the Gluster volume with "-o acl" instead. Maybe that common problem can be added?

Note that there are other references where bricks are mounted with "-o acl". "-o acl" is the default for XFS and most other filesystems, there is no need to explicitly mention or request it.

--- Additional comment from divya on 2012-09-04 07:44:38 EDT ---

I have deleted the sections which instructed users to mount with "-o acl" option and the updated documentation is available at: http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Storage/2.0/html/Administration_Guide/index.html

Comment 2 Divya 2012-10-03 10:26:17 UTC
I have deleted the sections which instructed users to mount with "-o acl" option and the updated documentation is available at: http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Storage/2.0/html/Administration_Guide/index.html

Comment 3 SATHEESARAN 2012-10-10 12:40:15 UTC
Moving this bug to VERIFIED state


Note You need to log in before you can comment on or make changes to this bug.