Bug 764986 (GLUSTER-3254)

Summary:	3.2.2 release notes (known issues), has an incorrect replace-brick command template.
Product:	[Community] Gluster-Documentation	Reporter:	krishnan parthasarathi <kparthas>
Component:	Release Notes	Assignee:	Divya <divya>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	gluster-bugs, nsathyan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description krishnan parthasarathi 2011-07-26 12:18:10 UTC

One of the 'known issues', bullet points reads as follows,
"... # gluster volume replace-brick <VOLNAME> commit command is issued, the file
system operations on that particular volume, which are in transit will fail.

Instead it should be, "... # gluster volume replace-brick <VOLNAME> <SRC-BRICK> <DST-BRICK> commit ..."

Comment 1 Divya 2011-09-22 06:17:49 UTC

I have updated the Known Issues section's bullet point as "... # gluster volume replace-brick VOLNAME BRICK NEW-BRICK commit ...". The changes will be reflected from 3.2.4 release.