Bug 809919

Summary:	Mark fd as bad if open(dir) fails during fd-migration after graph switch
Product:	[Community] GlusterFS	Reporter:	Raghavendra G <rgowdapp>
Component:	fuse	Assignee:	Raghavendra G <rgowdapp>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	pre-release	CC:	gluster-bugs, junaid
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-20 03:37:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Raghavendra G 2012-04-04 16:34:17 UTC

Description of problem:
During migration of fd after graph switch, if open(dir) fails, the fd is not marked as bad. Instead, future calls just pass through the new graph. With fdctx for protocol/client being NULL, the fd is treated as anonymous fd and the call fails/succeeds based on that treatment. However this behavior is not desired.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Raghavendra G 2012-04-04 16:36:55 UTC

Thanks to Junaid for pointing this bug out.

Comment 2 Anand Avati 2012-04-04 23:27:52 UTC

CHANGE: http://review.gluster.com/3085 (fuse-bridge/fd-migration: document migration failures in fdctx.) merged in master by Anand Avati (avati)

Comment 3 Junaid 2012-04-05 05:49:41 UTC

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