[Gluster-devel] valgrind report: LEAKY

[Michael Brown]

I've been having all sorts of trouble with glusterfs/nfs daemon on the
latest release-3.4 code (plus a few patches)

The actual code running here is
https://github.com/Supermathie/glusterfs/tree/release-3.4-oracle minus
bae32a5affd514e5a78ba3af6cc644cd5cd6814a.

Command run was:
valgrind --log-file=nfs.valgrind.log --leak-check=full
/usr/local/glusterfs/sbin/glusterfs -s localhost --volfile-id
gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid -l
/usr/local/glusterfs/var/log/glusterfs/nfs.log -S
/var/run/acea3a15b6c766d83c0bfefbe96e67e8.socket

Highlights include:
==31395== LEAK SUMMARY:
==31395== definitely lost: 22,068,769,377 bytes in 8,187,288 blocks
==31395== indirectly lost: 13,662,771 bytes in 1,085,883 blocks
==31395== possibly lost: 27,949,328 bytes in 10,696 blocks
==31395== still reachable: 117,519,648 bytes in 18,496 blocks

Workload is Oracle over DNFS.

M.

-- 
Michael Brown               | `One of the main causes of the fall of
Systems Consultant          | the Roman Empire was that, lacking zero,
Net Direct Inc.             | they had no way to indicate successful
☎: +1 519 883 1172 x5106    | termination of their C programs.' - Firth

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nfs.valgrind.log.gz
Type: application/x-gzip
Size: 18022 bytes
Desc: not available
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20130503/b4448f50/attachment-0001.gz>