Description of problem when replace-brick is performed, a glusterfs client process is started to migrate the data. executing "mount" command is displaying the replace-brick started glusterfs process also. This client process should not be displayed in the mount output as it is internal process started by replace-brick. Version-Release number of selected component (if applicable): mainline How reproducible: often Steps to Reproduce: 1.create a volume. start volume 2.perform replace-brick <old_brick> <new_brick> 3.execute "mount" command on the storage node where replace-brick is started. Actual results: [03/26/12 - 22:39:18 root@APP-SERVER1 dstore1]# mount /dev/sda3 on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext3 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /dev/sdb1 on /export1 type ext4 (rw) /dev/sdc1 on /export2 type xfs (rw) /etc/glusterd/vols/dstore/rb_client.vol on /etc/glusterd/vols/dstore/rb_mount type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072)
*** Bug 807650 has been marked as a duplicate of this bug. ***
CHANGE: http://review.gluster.com/3143 (glusterd: Modifed replace-brick mount cleanup to use lazy umount) merged in master by Anand Avati (avati)