Bug 804592

Summary:	Rename fails during graph change
Product:	[Community] GlusterFS	Reporter:	Anush Shetty <ashetty>
Component:	fuse	Assignee:	Raghavendra G <rgowdapp>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	amarts, gluster-bugs, rfortier, sasundar, vbellur, vkoppad
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	848326 (view as bug list)		Environment:
Last Closed:	2013-07-24 17:59:15 UTC	Type:	---
Regression:	---	Mount Type:	fuse
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	848326

Description Anush Shetty 2012-03-19 11:05:21 UTC

Description of problem: Renames fails with ENOENT while the graph change was going on. This was a single export volume.


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


How reproducible: Consistently


Steps to Reproduce:
1. while true; do echo 'sdsdsd' > dot; mv dot dot2; rm -rf *; done
2. while true; do gluster volume set test2 performance.write-behind off; sleep 1; gluster volume set test2 performance.write-behind on; sleep 1; done

3.
  
Actual results:

mv: cannot move `dot' to `dot2': No such file or directory


Expected results:

Renames should continue without errors.


Additional info:

Client log:

[2012-03-19 16:31:06.223804] E [fuse-bridge.c:1511:fuse_rename_resume] 0-glusterfs-fuse: RENAME 45223 00000000-0000-0000-0000-000000000000/do
t -> 00000000-0000-0000-0000-000000000000/dot2 src resolution failed
[2012-03-19 16:31:06.229473] E [fuse-bridge.c:1329:fuse_unlink_resume] 0-glusterfs-fuse: UNLINK 1 (00000000-0000-0000-0000-000000000000/dot) 
resolution failed
[2012-03-19 16:31:06.235730] E [fuse-bridge.c:1511:fuse_rename_resume] 0-glusterfs-fuse: RENAME 45240 00000000-0000-0000-0000-000000000000/do
t -> 00000000-0000-0000-0000-000000000000/dot2 src resolution failed
[2012-03-19 16:31:06.243696] E [fuse-bridge.c:1329:fuse_unlink_resume] 0-glusterfs-fuse: UNLINK 1 (00000000-0000-0000-0000-000000000000/dot) 
resolution failed
[2012-03-19 16:31:06.249440] E [fuse-bridge.c:1511:fuse_rename_resume] 0-glusterfs-fuse: RENAME 45257 00000000-0000-0000-0000-000000000000/do
t -> 00000000-0000-0000-0000-000000000000/dot2 src resolution failed
[2012-03-19 16:31:06.252887] E [fuse-bridge.c:1329:fuse_unlink_resume] 0-glusterfs-fuse: UNLINK 1 (00000000-0000-0000-0000-000000000000/dot) 
resolution failed
[2012-03-19 16:31:06.259771] E [fuse-bridge.c:1511:fuse_rename_resume] 0-glusterfs-fuse: RENAME 45274 00000000-0000-0000-0000-000000000000/do
t -> 00000000-0000-0000-0000-000000000000/dot2 src resolution failed
[2012-03-19 16:31:06.262661] E [fuse-bridge.c:1329:fuse_unlink_resume] 0-glusterfs-fuse: UNLINK 1 (00000000-0000-0000-0000-000000000000/dot) 
resolution failed
[2012-03-19 16:31:06.271101] E [fuse-bridge.c:1511:fuse_rename_resume] 0-glusterfs-fuse: RENAME 45291 00000000-0000-0000-0000-000000000000/do
t -> 00000000-0000-0000-0000-000000000000/dot2 src resolution failed
[2012-03-19 16:31:06.273614] E [fuse-bridge.c:1329:fuse_unlink_resume] 0-glusterfs-fuse: UNLINK 1 (00000000-0000-0000-0000-000000000000/dot) 
resolution failed
[2012-03-19 16:31:06.277884] E [fuse-bridge.c:1511:fuse_rename_resume] 0-glusterfs-fuse: RENAME 45308 00000000-0000-0000-0000-000000000000/do
t -> 00000000-0000-0000-0000-000000000000/dot2 src resolution failed
[2012-03-19 16:31:06.280381] E [fuse-bridge.c:1329:fuse_unlink_resume] 0-glusterfs-fuse: UNLINK 1 (00000000-0000-0000-0000-000000000000/dot) 
resolution failed

Comment 1 Amar Tumballi 2012-03-25 07:14:16 UTC

Check if its already fixed.

Comment 2 Anush Shetty 2012-03-26 05:00:36 UTC

This issue still exists on the mainline.

Comment 3 Raghavendra G 2012-04-03 03:35:05 UTC

Patch has been sent for review at http://review.gluster.com/#change,3007

Comment 4 Anush Shetty 2012-04-23 07:07:12 UTC

With http://review.gluster.com/#change,3181 and http://review.gluster.com/#change,3181, this issue is fixed.

Comment 5 Anush Shetty 2012-04-23 07:08:09 UTC

With http://review.gluster.com/#change,3007 and  http://review.gluster.com/#change,3181 I meant.

Comment 6 Anand Avati 2012-05-08 22:34:57 UTC

CHANGE: http://review.gluster.com/3007 (fuse-resolve: consider cases where an entry should be resolved even when parent belongs to active itable.) merged in master by Anand Avati (avati)

Comment 7 Anand Avati 2012-05-16 00:09:15 UTC

CHANGE: http://review.gluster.com/3181 (fuse-resolve: Attempt fd-migration in resolver, if migration was never attempted.) merged in master by Anand Avati (avati)

Comment 8 Vijay Bellur 2012-05-18 13:12:23 UTC

Addressing this post 3.3.0.

Comment 9 Raghavendra G 2012-08-29 09:17:15 UTC

*** Bug 827405 has been marked as a duplicate of this bug. ***

Comment 10 Amar Tumballi 2012-10-11 09:40:16 UTC

*** Bug 860140 has been marked as a duplicate of this bug. ***