Bug 796116 - Graph switching is not happening properly
Summary: Graph switching is not happening properly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: fuse
Version: mainline
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Raghavendra G
QA Contact: shylesh
URL:
Whiteboard:
: 798198 (view as bug list)
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-02-22 10:54 UTC by shylesh
Modified: 2013-07-24 17:22 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:22:24 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description shylesh 2012-02-22 10:54:04 UTC
Description of problem:
In order to get effect new graph we have to remount 

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

How reproducible:
Always

Steps to Reproduce:
1. Create a distribute volume with 1 brick
2. created 100 files of 10M each on the mount point 
3. add two more bricks to the volume
4. Initiate rebalance 
5. After rebalance is completed check number of files on the mount point
  
Actual results:
Number files on the mount point will be lesser than actually created.
Upon remounting number of files shown will be proper.

Expected results:


Additional info:

This is because looup() are sent on the old graph not the new one, this is regression introduced by the commit 8e81cbacc53adc77bc4eabb5a26d6d13012f5f86
 "fuse: fix resolver to handle graph switches properly"  BUG: 785675

Comment 1 Kaushal 2012-02-28 11:33:03 UTC
*** Bug 798198 has been marked as a duplicate of this bug. ***

Comment 2 Raghavendra G 2012-03-20 02:08:01 UTC
Shylesh,

On 65c6e3706f5290947179922c, this problem is not found. Can you confirm that this problem does not appear on the above said commit?

regards,
Raghavendra.

Comment 3 shylesh 2012-05-24 05:52:39 UTC
This bug is not reproducible on 3.3.0qa42


Note You need to log in before you can comment on or make changes to this bug.