Bug 764485 (GLUSTER-2753) - perf-test failed with "buf is null!" message
Summary: perf-test failed with "buf is null!" message
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2753
Product: GlusterFS
Classification: Community
Component: unclassified
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-14 07:18 UTC by M S Vishwanath Bhat
Modified: 2016-06-01 01:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description M S Vishwanath Bhat 2011-04-14 07:18:54 UTC
perf-test failed with profile ON with qa10 code with the "buf is null!" message. The first fail happened during the large file delete with profile ON. 

running largefile_reread ... done (5.93 secs)
running largefile_delete ... FAILED!!!

The following message appears many times in logs.

[2011-04-12 06:51:23.865109] W [dict.c:2458:dict_unserialize] (-->/usr/local/lib/libgfrpc.so.0(rpcsvc_notify+0x181) [0x7f731c151836] (-->/usr/local/lib/libgfrpc.so.0(rpcsvc_handle_rpc_call+0x344) [0x7f731c151493] (-->/usr/local/lib/glusterfs/3.2.0qa10/xlator/mgmt/glusterd.so(glusterd_handle_cli_profile_volume+0x305) [0x7f731a5827d2]))) 0-dict: buf is null!

I have archived the logs since it's too big to upload. 

This issue is not reproducible every time with latest code. But when i scheduled 6 runs of perf-test overnight, it failed 3 times.

Comment 1 Anand Avati 2011-04-14 08:07:47 UTC
PATCH: http://patches.gluster.com/patch/6875 in master (mgmt/glusterd: Prevent dict unserialize for buf with 0 length)

Comment 2 M S Vishwanath Bhat 2011-04-16 05:43:12 UTC
Tested with qa12 and all the scheduled 6 runs of perf-test passed.


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