Bug 1325810 - Invalid argument in logs
Summary: Invalid argument in logs
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: marker
Version: 3.7.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-11 09:26 UTC by Dmitry Melekhov
Modified: 2017-03-08 10:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-08 10:50:07 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Dmitry Melekhov 2016-04-11 09:26:12 UTC 
Description of problem:

We are using gluster 3.7.10 in centos 7 hosts with qemu and get this in logs:

[2016-04-11 09:16:03.000596] I [dict.c:473:dict_get] (-->/lib64/libglusterfs.so.0(default_getxattr_cbk+0xac) [0x7f834dc3ac8c] -->/usr/lib64/glusterfs/3.7.10/xlator/feat
ures/marker.so(marker_getxattr_cbk+0xa7) [0x7f833a048857] -->/lib64/libglusterfs.so.0(dict_get+0xac) [0x7f834dc2b0cc] ) 0-dict: !this || key=() [Invalid argument]

very often.

Looks like bug.

Don't know which operation results in this output though.

Thank you!
Comment 1 Vijaikumar Mallikarjuna 2016-04-12 12:44:07 UTC 
This is a duplicate of bug# 1319581
Comment 2 Kaushal 2017-03-08 10:50:07 UTC 
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.
Note You need to log in before you can comment on or make changes to this bug.