Hi Vijay,
I make following test:
Start glusterfs volume, kill glusterfsd, and start glusterfsd with following command:
valgrind --log-file=/root/dingyuan/logs/valgrind.log /usr/sbin/glusterfsd -s server241 --volfile-id vol1.server241.fsmnt-fs1 -p /var/lib/glusterd/vols/vol1/run/server241-fsmnt-fs1.pid -S /var/run/4f8241255dc7142a794af68d66dcedeb.socket --brick-name /fsmnt/fs1 -l /var/log/glusterfs/bricks/fsmnt-fs1.log --xlator-option *-posix.glusterd-uuid=41da2eae-c2c8-41a0-8873-5286699a8b95 --brick-port 49153 --xlator-option vol1-server.listen-port=49153 -N
The command line option is the same with default command line option except the red region.
Then mount nfs client, run ltp test.
After a few minutes, valgrind seems run into a dead loop. top shows below:(glusterfsd run in the process 'memcheck-amd64-')
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
21255 root 20 0 309m 106m 4328 R 100.1 1.4 1121:42 memcheck-amd64-
The process can not be killed by SIGTERM. SIGKILL can kill it, but no valgrind report generated...
Is there something wrong with my test procedure. Or is there other method to catch more information?
Thanks!