Hi Team, I upload some valgrind logs from my gluster 5.4 setup. This is writing to the volume every 15 minutes. I stopped glusterd and then copy away the logs. The test was running for some simulated days. They are zipped in valgrind-54.zip. Lots of info in valgrind-2730.log. Lots of possibly lost bytes in glusterfs and even some definitely lost bytes. ==2737== 1,572,880 bytes in 1 blocks are possibly lost in loss record 391 of 391 ==2737== at 0x4C29C25: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==2737== by 0xA22485E: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA217C94: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA21D9F8: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA21DED9: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA21E685: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA1B9D8C: init (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0x4E511CE: xlator_init (in /usr/lib64/libglusterfs.so.0.0.1) ==2737== by 0x4E8A2B8: ??? (in /usr/lib64/libglusterfs.so.0.0.1) ==2737== by 0x4E8AAB3: glusterfs_graph_activate (in /usr/lib64/libglusterfs.so.0.0.1) ==2737== by 0x409C35: glusterfs_process_volfp (in /usr/sbin/glusterfsd) ==2737== by 0x409D99: glusterfs_volumes_init (in /usr/sbin/glusterfsd) ==2737===2737== LEAK SUMMARY: ==2737== definitely lost: 1,053 bytes in 10 blocks ==2737== indirectly lost: 317 bytes in 3 blocks ==2737== possibly lost: 2,374,971 bytes in 524 blocks ==2737== still reachable: 53,277 bytes in 201 blocks ==2737== suppressed: 0 bytes in 0 blocks -- Regards Abhishek Paliwal -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190516/b81a0ba8/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: valgrind-2748.log Type: text/x-log Size: 23721 bytes Desc: not available URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190516/b81a0ba8/attachment-0003.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: valgrind-2746.log Type: text/x-log Size: 24526 bytes Desc: not available URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190516/b81a0ba8/attachment-0004.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: valgrind-2730.log Type: text/x-log Size: 1239130 bytes Desc: not available URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190516/b81a0ba8/attachment-0005.bin>
Anyone please reply.... On Thu, May 16, 2019, 10:49 ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote:> Hi Team, > > I upload some valgrind logs from my gluster 5.4 setup. This is writing to > the volume every 15 minutes. I stopped glusterd and then copy away the > logs. The test was running for some simulated days. They are zipped in > valgrind-54.zip. > > Lots of info in valgrind-2730.log. Lots of possibly lost bytes in > glusterfs and even some definitely lost bytes. > > ==2737== 1,572,880 bytes in 1 blocks are possibly lost in loss record 391 > of 391 > ==2737== at 0x4C29C25: calloc (in > /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) > ==2737== by 0xA22485E: ??? (in > /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) > ==2737== by 0xA217C94: ??? (in > /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) > ==2737== by 0xA21D9F8: ??? (in > /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) > ==2737== by 0xA21DED9: ??? (in > /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) > ==2737== by 0xA21E685: ??? (in > /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) > ==2737== by 0xA1B9D8C: init (in > /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) > ==2737== by 0x4E511CE: xlator_init (in /usr/lib64/libglusterfs.so.0.0.1) > ==2737== by 0x4E8A2B8: ??? (in /usr/lib64/libglusterfs.so.0.0.1) > ==2737== by 0x4E8AAB3: glusterfs_graph_activate (in > /usr/lib64/libglusterfs.so.0.0.1) > ==2737== by 0x409C35: glusterfs_process_volfp (in /usr/sbin/glusterfsd) > ==2737== by 0x409D99: glusterfs_volumes_init (in /usr/sbin/glusterfsd) > ==2737=> ==2737== LEAK SUMMARY: > ==2737== definitely lost: 1,053 bytes in 10 blocks > ==2737== indirectly lost: 317 bytes in 3 blocks > ==2737== possibly lost: 2,374,971 bytes in 524 blocks > ==2737== still reachable: 53,277 bytes in 201 blocks > ==2737== suppressed: 0 bytes in 0 blocks > > -- > > > > > Regards > Abhishek Paliwal >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190517/6e7de06c/attachment.html>
Hi Team, Please respond on the issue which I raised. Regards, Abhishek On Fri, May 17, 2019 at 2:46 PM ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote:> Anyone please reply.... > > On Thu, May 16, 2019, 10:49 ABHISHEK PALIWAL <abhishpaliwal at gmail.com> > wrote: > >> Hi Team, >> >> I upload some valgrind logs from my gluster 5.4 setup. This is writing to >> the volume every 15 minutes. I stopped glusterd and then copy away the >> logs. The test was running for some simulated days. They are zipped in >> valgrind-54.zip. >> >> Lots of info in valgrind-2730.log. Lots of possibly lost bytes in >> glusterfs and even some definitely lost bytes. >> >> ==2737== 1,572,880 bytes in 1 blocks are possibly lost in loss record 391 >> of 391 >> ==2737== at 0x4C29C25: calloc (in >> /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) >> ==2737== by 0xA22485E: ??? (in >> /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) >> ==2737== by 0xA217C94: ??? (in >> /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) >> ==2737== by 0xA21D9F8: ??? (in >> /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) >> ==2737== by 0xA21DED9: ??? (in >> /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) >> ==2737== by 0xA21E685: ??? (in >> /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) >> ==2737== by 0xA1B9D8C: init (in >> /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) >> ==2737== by 0x4E511CE: xlator_init (in /usr/lib64/libglusterfs.so.0.0.1) >> ==2737== by 0x4E8A2B8: ??? (in /usr/lib64/libglusterfs.so.0.0.1) >> ==2737== by 0x4E8AAB3: glusterfs_graph_activate (in >> /usr/lib64/libglusterfs.so.0.0.1) >> ==2737== by 0x409C35: glusterfs_process_volfp (in /usr/sbin/glusterfsd) >> ==2737== by 0x409D99: glusterfs_volumes_init (in /usr/sbin/glusterfsd) >> ==2737=>> ==2737== LEAK SUMMARY: >> ==2737== definitely lost: 1,053 bytes in 10 blocks >> ==2737== indirectly lost: 317 bytes in 3 blocks >> ==2737== possibly lost: 2,374,971 bytes in 524 blocks >> ==2737== still reachable: 53,277 bytes in 201 blocks >> ==2737== suppressed: 0 bytes in 0 blocks >> >> -- >> >> >> >> >> Regards >> Abhishek Paliwal >> >-- Regards Abhishek Paliwal -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190604/5ad12d8a/attachment.html>