Description of problem: ======================== NFS Log file reporting following warning message whenever a file is modified when one of the brick is offline in a replicate volume (1x2). [2012-11-04 05:17:34.161255] W [client3_1-fops.c:2630:client3_1_lookup_cbk] 0-rep_new-client-1: remote operation failed: Invalid argument. Path: /test_data_self_heal/file.93 (e555ef32-dc93-4461-acd7-816df26ae266) [2012-11-04 05:17:34.161319] W [nfs3.c:707:nfs3svc_getattr_lookup_cbk] 0-nfs: 29dba4c: /test_data_self_heal/file.93 => -1 (Invalid argument) [2012-11-04 05:17:34.161342] W [nfs3-helpers.c:3389:nfs3_log_common_res] 0-nfs-nfsv3: XID: 29dba4c, GETATTR: NFS: 22(Invalid argument for operation), POSIX: 22(Invalid argument) Version-Release number of selected component (if applicable): ============================================================= [11/04/12 - 04:07:56 root@darrel ~]# gluster --version glusterfs 3.3.0.5rhs built on Nov 2 2012 01:29:35 [11/04/12 - 04:11:02 root@darrel ~]# rpm -qa | grep gluster glusterfs-3.3.0.5rhs-35.el6rhs.x86_64 glusterfs-server-3.3.0.5rhs-35.el6rhs.x86_64 How reproducible: ================= Often script1.sh:- ============= mkdir test_data_self_heal; cd test_data_self_heal ; for i in `seq 1 100`; do dd if=/dev/input_file of=file.$i bs=128K count=$i; done; cd ../ script2.sh:- ============ cd test_data_self_heal; for i in `seq 1 100`; do dd if=/dev/input_file of=file.$i bs=512K count=$i; done; cd ../ Steps to Reproduce: ==================== 1.create a pure replicate volume (1x2). start the volume 2.create a nfs mount from the client. 3.execute "script1.sh" from the nfs mount 4.After execution of "script1.sh", bring down brick1 5.executed "script2.sh" from nfs mount Actual results: ================ [2012-11-04 05:17:34.161255] W [client3_1-fops.c:2630:client3_1_lookup_cbk] 0-rep_new-client-1: remote operation failed: Invalid argument. Path: /test_data_self_heal/file.93 (e555ef32-dc93-4461-acd7-816df26ae266) [2012-11-04 05:17:34.161319] W [nfs3.c:707:nfs3svc_getattr_lookup_cbk] 0-nfs: 29dba4c: /test_data_self_heal/file.93 => -1 (Invalid argument) [2012-11-04 05:17:34.161342] W [nfs3-helpers.c:3389:nfs3_log_common_res] 0-nfs-nfsv3: XID: 29dba4c, GETATTR: NFS: 22(Invalid argument for operation), POSIX: 22(Invalid argument) Expected results: ================== There is no failure in the "dd" command execution on the file. But still , nfs log message says "Invalid Argument" and "remote operation failed". what does this really mean ?
This is another symptom of https://bugzilla.redhat.com/show_bug.cgi?id=872923. The fix for 872923 works to alleviate these messages too. *** This bug has been marked as a duplicate of bug 872923 ***
From QA it is confirmed that issue is because of the bug 872923. The fix for 872923 fixes the NFS Log file reporting following warning message : "remote operation failed: Invalid argument"