[Bugs] [Bug 1242708] New: fuse/fuse_thread_proc : The fuse_graph_sync function cannot be handled in time after we fix-layout.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1242708

            Bug ID: 1242708
           Summary: fuse/fuse_thread_proc : The fuse_graph_sync function
                    cannot be handled  in time after we fix-layout.
           Product: GlusterFS
           Version: pre-release
         Component: fuse
          Assignee: bugs at gluster.org
          Reporter: linux_wz at 163.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
After we add-brick and fix-layout,the function fuse_thread_proc is still
blocked in readv,The old graph will be executed first.The first time we create
a file on the client, we will get an incorrect hash volume.


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

Steps to Reproduce:
1.[node1]# gluster volume info
  Volume Name: dht_vol
  Type: Distribute
  Volume ID: f99cc88b-9558-4286-a56e-3bcb7d057035
  Status: Started
  Number of Bricks: 1
  Transport-type: tcp
  Bricks:
  Brick1: 10.10.21.150:/root/sdb
  Options Reconfigured:
  performance.readdir-ahead: on
2.[node3]# mount.glusterfs node1:/dht_vol /mnt/gluster/
3.[node1]# gluster volume add-brick dht_vol 10.10.21.150:/root/sdc force
  [node1]# gluster volume rebalance dht_vol fix-layout start
4.[node3]# touch 0
5.[node1]# ls  sd*
  sdb:

  sdc:
  0
6.[node3]# rm 0 -rf; touch 0
7.[root at node1 ~]# ls  sd*
  sdb:
  0
  sdc:

Actual results:
step 3-4: the first time we create a file, 0 is distributed in sdc.
step 5-6: but the second time,file 0 is distributed in sdb

Expected results:
step 5-6: We hope file 0 should belong to the same brick

Additional info:
I have a solution for this problem.we can move the function fuse_graph_sync
back
to readv .I've tested it, it's right.But I don't know if it will bring other
problems. Waiting for your answer. Thank you.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.