Bug 981615 - afr: commit failed when invoked gluster volume heal <vol-name> but no error reported, it reported (ERROR : )
Summary: afr: commit failed when invoked gluster volume heal <vol-name> but no error r...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: replicate
Version: 2.1
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Ravishankar N
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-05 09:45 UTC by Rahul Hinduja
Modified: 2016-09-19 22:07 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-03 17:13:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Rahul Hinduja 2013-07-05 09:45:55 UTC
Description of problem:
=======================

afr: commit failed when invoked gluster volume heal <vol-name> but no error reported, it just reported (ERROR : )

Log Snippet:
============

[2013-07-05 19:03:28.629044] E [glusterd-syncop.c:681:_gd_syncop_commit_op_cbk] 0-management: Commit failed on 10.70.36.35. Error : 
[2013-07-05 19:03:55.145183] I [glusterd-volume-ops.c:478:__glusterd_handle_cli_heal_volume] 0-management: Received heal vol req for volume vol-dr
[2013-07-05 19:03:55.156450] E [glusterd-syncop.c:681:_gd_syncop_commit_op_cbk] 0-management: Commit failed on 10.70.36.35. Error : 
[2013-07-05 19:04:52.639686] I [glusterd-volume-ops.c:478:__glusterd_handle_cli_heal_volume] 0-management: Received heal vol req for volume vol-dr
[2013-07-05 19:04:52.651064] E [glusterd-syncop.c:681:_gd_syncop_commit_op_cbk] 0-management: Commit failed on 10.70.36.35. Error : 

Looking into the logs above I am not sure why the error is reported and cli failed. As mentioned above the Error is (Error : )


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

glusterfs-devel-3.4.0.12rhs.beta2-1.el6rhs.x86_64
glusterfs-3.4.0.12rhs.beta2-1.el6rhs.x86_64
glusterfs-server-3.4.0.12rhs.beta2-1.el6rhs.x86_64
glusterfs-geo-replication-3.4.0.12rhs.beta2-1.el6rhs.x86_64
glusterfs-debuginfo-3.4.0.12rhs.beta2-1.el6rhs.x86_64
glusterfs-fuse-3.4.0.12rhs.beta2-1.el6rhs.x86_64
glusterfs-rdma-3.4.0.12rhs.beta2-1.el6rhs.x86_64



Steps Carried:
==============
1. Created and started 6*2 volume from server1-4.
2. Mounted on Fuse and NFS client
3. Created f and n directory from NFS mount
4. Cd to f from fuse and cd to n from nfs client.
5. Created directories and files from the mount points
6. killed bricks from server 4 (kill -9)
7. powered down server 2 (poweroff)
8. performed operations from fuse client like setfattr, setfattr -x to have metadata change.
9. Restarted the volume forcefully to online the brick process of server 4.
10. Tried to execute the heal command from server 3.

# gluster volume heal vol-dr
Commit failed on 10.70.36.35. Please check the log file for more details.


Actual results:
===============

[2013-07-05 19:03:28.629044] E [glusterd-syncop.c:681:_gd_syncop_commit_op_cbk] 0-management: Commit failed on 10.70.36.35. Error : 
[2013-07-05 19:03:55.145183] I [glusterd-volume-ops.c:478:__glusterd_handle_cli_heal_volume] 0-management: Received heal vol req for volume vol-dr
[2013-07-05 19:03:55.156450] E [glusterd-syncop.c:681:_gd_syncop_commit_op_cbk] 0-management: Commit failed on 10.70.36.35. Error : 
[2013-07-05 19:04:52.639686] I [glusterd-volume-ops.c:478:__glusterd_handle_cli_heal_volume] 0-management: Received heal vol req for volume vol-dr
[2013-07-05 19:04:52.651064] E [glusterd-syncop.c:681:_gd_syncop_commit_op_cbk] 0-management: Commit failed on 10.70.36.35. Error : 

Expected results:
=================

I am not sure why the commit should fail here. If it is expected to fail than it should have been reported properly in logs, just not Error : 

No error is reported in logs.

Comment 4 Vivek Agarwal 2015-12-03 17:13:36 UTC
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.


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