Bug 812199

Created attachment 577222 [details]
Mount log file

Description of problem:
------------------------

1) The log message reports Path as 'null'. Either it should report gfid of that path or the path name itself.

2) numerous entries of the below mentioned log message is reported in the mount log. should be handled in a better way. 

[2012-04-12 23:58:22.777865] W [client3_1-fops.c:1054:client3_1_getxattr_cbk] 0-dstore-client-0: remote operation failed: No data available. Path: (null)
[2012-04-12 23:58:22.778407] W [client3_1-fops.c:1054:client3_1_getxattr_cbk] 0-dstore-client-2: remote operation failed: No data available. Path: (null)
[2012-04-12 23:58:22.806044] W [client3_1-fops.c:1054:client3_1_getxattr_cbk] 0-dstore-client-1: remote operation failed: No data available. Path: (null)


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

How reproducible:
----------------
often

run_dbench.sh:-
---------------
#!/bin/bash

while true;
	do
	dbench -s -F -S --stat-check 10
	dbench -s -F -S -x --one-byte-write-fix --stat-check 10
	done

Steps to Reproduce:
---------------------
1.create a replicate volume (1X3).start the volume
2.create fuse mount. 
3.execute "run_dbench.sh" on fuse mount. 
  
Actual results:
---------------
continuously reports "remote operation failed: No data available. Path: (null)" because application was unable to perform setxattr, getxattr operations. Refer to Bug811957

Additional Info:-
-------------------
[04/13/12 - 15:11:07 root@APP-SERVER1 ~]# gluster volume info
 
Volume Name: dstore
Type: Replicate
Volume ID: bfddf295-51a2-48ab-b048-cd7dcfa3f91e
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: 192.168.2.35:/export1/dstore1
Brick2: 192.168.2.36:/export1/dstore1
Brick3: 192.168.2.37:/export1/dstore1

------------------