Bug 1781318 - [disperse-logging]: show the gfid for which the version and size update failed
Summary: [disperse-logging]: show the gfid for which the version and size update failed
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-09 18:25 UTC by Raghavendra Bhat
Modified: 2020-03-12 13:24 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-12 13:24:48 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23840 0 None Abandoned cluster/ec: log the gfid when updating size and version fails. 2019-12-12 15:28:34 UTC

Description Raghavendra Bhat 2019-12-09 18:25:10 UTC 
Description of problem:

In erasure coding translator, when updating the version and size fails, the error message does not contain the gfid of the object for which the update failed.
This helps in debugging.


Example:

[2019-11-18 08:41:37.797426] E [MSGID: 122037] [ec-common.c:1914:ec_update_size_version_done] 0-gdp_llk-disperse-5: Failed to update version and size [Input/output error]

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Worker Ant 2019-12-09 19:03:40 UTC 
REVIEW: https://review.gluster.org/23840 (cluster/ec: log the gfid when updating size and version fails.) posted (#1) for review on master by Raghavendra Bhat
Comment 2 Worker Ant 2020-03-12 13:24:48 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/1012, and will be tracked there from now on. Visit GitHub issues URL for further details
Note You need to log in before you can comment on or make changes to this bug.