Bug 814809 - Users don't understand that you cannot write to bricks
Users don't understand that you cannot write to bricks
Status: ON_QA
Product: Gluster-Documentation
Classification: Community
Component: Other (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Divya
Depends On:
  Show dependency treegraph
Reported: 2012-04-20 14:24 EDT by Joe Julian
Modified: 2016-01-11 03:46 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joe Julian 2012-04-20 14:24:35 EDT
On http://download.gluster.org/pub/gluster/glusterfs/3.2/Documentation/AG/html/chap-Administration_Guide-Setting_Volumes.html a warning should be added to prevent customers from expecting replication of changes made directly to bricks.

A volume is a logical collection of bricks where each brick is an export directory on a server in the trusted storage pool. Most of the gluster management operations happen on the volume.


You can create new volumes in your storage environment, as needed. When creating a new volume, you must specify the bricks that comprise the volume.

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