Vijay, I have been testing gluster-3.3.0qa39 NFS with 4 CentOS 6.2 NFS clients. The test set is like following: 1) All 4 clients mount 64 directories. (total 192 directories) 2) 192 procs runs on the 4 clients. each proc create a new unique file and write 1GB data to the file. (total 192GB) 3) All 4 clients umount 64 directories. The test finished successfully but showmount command reported many entries in spite of there were no NFS clients remain. Then I have restarted gluster related daemons. After restarting, showmount command reports no entries. Any insight into this is much appreciated. [root@172 ~]# showmount | wc -l 164 [root@172 ~]# ps axl | egrep "RSS|gluster" F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 5 0 7201 1 15 0 100280 10732 - Ssl ? 0:00 /usr/sbin/glusterd --pid-file=/var/run/glusterd.pid --log-level=DEBUG 5 0 7217 1 15 0 367628 24108 - Ssl ? 28:58 /usr/sbin/glusterfsd -s localhost --volfile-id four.four-2-private.mnt-brick -p /var/lib/glusterd/vols/four/run/four-2-private-mnt-brick.pid -S /tmp/7d429a2d2efb6e33b3e4dba9f6996a3e.socket --brick-name /mnt/brick -l /var/log/glusterfs/bricks/mnt-brick.log --xlator-option *-posix.glusterd-uuid=9d122d90-b451-47ab-afef-8f5dc7d1d05c --brick-port 24009 --xlator-option four-server.listen-port=24009 5 0 7223 1 15 0 230176 46008 - Ssl ? 14:15 /usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log -S /tmp/32bec3aa1764f5bd30a5add89ce32b45.socket 0 0 17680 17602 18 0 6064 644 pipe_w S+ pts/0 0:00 egrep RSS|gluster [root@172 ~]# /etc/init.d/glusterd restart Stopping glusterd: [ OK ] Starting glusterd: [ OK ] [root@172 ~]# showmount | wc -l 1 [root@172 ~]# ps axl | egrep "RSS|gluster" F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 5 0 17713 1 15 0 100336 10764 - Ssl ? 0:00 /usr/sbin/glusterd --pid-file=/var/run/glusterd.pid --log-level=DEBUG 5 0 17720 1 17 0 124224 15672 - Ssl ? 0:00 /usr/sbin/glusterfsd -s localhost --volfile-id four.four-2-private.mnt-brick -p /var/lib/glusterd/vols/four/run/four-2-private-mnt-brick.pid -S /tmp/7d429a2d2efb6e33b3e4dba9f6996a3e.socket --brick-name /mnt/brick -l /var/log/glusterfs/bricks/mnt-brick.log --xlator-option *-posix.glusterd-uuid=9d122d90-b451-47ab-afef-8f5dc7d1d05c --brick-port 24009 --xlator-option four-server.listen-port=24009 5 0 17726 1 15 0 161528 39592 - Ssl ? 0:00 /usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log -S /tmp/32bec3aa1764f5bd30a5add89ce32b45.socket 0 0 17747 17602 18 0 6064 640 pipe_w S+ pts/0 0:00 egrep RSS|gluster [root@172 ~]# Thanks, Tomo Sato
http://bits.gluster.com/pub/gluster/glusterfs/3.3.0qa39/ http://bits.gluster.com/pub/gluster/glusterfs/src/glusterfs-3.3.0qa39.tar.gz This release is made off v3.3.0qa39 _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxx https://lists.nongnu.org/mailman/listinfo/gluster-devel
