Hide Forgot
I ran volume top write-perf bs 1024 count 100 and it resulted in memory corruption core dumped. I got the following output [root@FC-2 vishwa]# gluster volume top hosdu write-perf bs 1024 count 100 gluster: mem-pool.c:270: __gf_free: Assertion `0' failed. Aborted (core dumped)
PATCH: http://patches.gluster.com/patch/6685 in master (Replace strdup call to gf_strdup as GF_FREE is being called)
Now volume top write-perf is not resulting in memory corruption. Also passing block 0 and count 0 doesn't result in 'nan' being listed. root@tortuga:/disk1# gluster volume top hosdu write-perf bs 0 count 100 block size should be an integer greater than zero Usage: volume top <VOLNAME> {[open|read|write|opendir|readdir] |[read-perf|write-perf bs <size> count <count>]} [brick <brick>] [list-cnt <count>] root@tortuga:/disk1# gluster volume top hosdu write-perf bs 1024 count 0 count should be an integer greater zero Usage: volume top <VOLNAME> {[open|read|write|opendir|readdir] |[read-perf|write-perf bs <size> count <count>]} [brick <brick>] [list-cnt <count>] Working as expected.