Bug 809919 - Mark fd as bad if open(dir) fails during fd-migration after graph switch
Summary: Mark fd as bad if open(dir) fails during fd-migration after graph switch
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: fuse
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
: 810079 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-04 16:34 UTC by Raghavendra G
Modified: 2012-04-20 03:37 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-04-20 03:37:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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. ***
Note You need to log in before you can comment on or make changes to this bug.