Bug 763711 (GLUSTER-1979)

Summary:	few issues with scale-n-defrag 3.0.6rc1
Product:	[Community] GlusterFS	Reporter:	Lakshmipathi G <lakshmipathi>
Component:	distribute	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.0.5	CC:	gluster-bugs, vijay, vraman
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:		Type:	---
Regression:	RTP	Mount Type:	fuse
Documentation:	DNR	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Lakshmipathi G 2010-10-19 09:54:29 UTC

few issues with scale-n-defrag script:

*files from root dir (/mnt) files are not distributed.

*if scale-n-defrag fails cd command (ex cd /mnt/ ) with nfs-stale error message.
then defrag script  executed on current directory - which is not glusterfs 

*log files are created for each file instead of  directory,like
-------------------------------
Completed directory /data/test2/files/f1399
Defragmenting directory /data/test2/files/f14 (/data/defrag-store-f14.log)
Completed directory /data/test2/files/f14
Defragmenting directory /data/test2/files/f140 (/data/defrag-store-f140.log)

Comment 1 Amar Tumballi 2010-11-09 02:55:06 UTC

This bug is open for 'DP' (Documentation Pending). As of now, there is no revalidate sent on 'root' inode in 3.0.x, hence the issue of ESTALE when the scale-n-defrag is run on the mountpoint directly.

Comment 2 Amar Tumballi 2011-01-21 07:41:12 UTC

We have marked our 3.0.x documentation as out of date, hence no more update is happening here. This issue is not seen in 3.1.x releases, hence closing the bug.

http://www.gluster.com/community/documentation/index.php/Gluster_3.0.x_Documentation

http://www.gluster.com/community/documentation/index.php/GlusterFS_User_Guide

Comment 3 Amar Tumballi 2011-03-22 06:55:47 UTC

As updated in the previous comment, we are not planing to update docs for 3.0.x release, and hence DP -> DNR..