Red Hat Bugzilla – Bug 1312834
USS-CIFS: snapd getting wrong process id after glusterd restart
Last modified: 2017-03-08 06:00:58 EST
Description of problem: After gluster restart, gluster v status and ps | grep snapd show different process id for snapd Version-Release number of selected component (if applicable): [root@rhs-client46 glusterfs]# rpm -qa | grep glusterfs glusterfs-3.7.8-1.el7.x86_64 glusterfs-server-3.7.8-1.el7.x86_64 glusterfs-geo-replication-3.7.8-1.el7.x86_64 glusterfs-cli-3.7.8-1.el7.x86_64 glusterfs-debuginfo-3.7.8-1.el7.x86_64 glusterfs-api-3.7.8-1.el7.x86_64 glusterfs-devel-3.7.8-1.el7.x86_64 glusterfs-rdma-3.7.8-1.el7.x86_64 glusterfs-libs-3.7.8-1.el7.x86_64 glusterfs-api-devel-3.7.8-1.el7.x86_64 glusterfs-client-xlators-3.7.8-1.el7.x86_64 glusterfs-extra-xlators-3.7.8-1.el7.x86_64 glusterfs-fuse-3.7.8-1.el7.x86_64 glusterfs-ganesha-3.7.8-1.el7.x86_64 samba-vfs-glusterfs-4.2.4-13.el7rhgs.x86_64 How reproducible: intermittent Steps to Reproduce: 1. Create 2*2 distribute replicate volume 2. Enable USS and quota 3. restart glusterd Actual results: Snapd has two different process id gluster v status and ps | grep snapd Expected results: gluster v status command and ps | grep snapd should show same snapd process id Additional info:
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.