email on gluster-users mailing list: Subject: Re: [Gluster-users] Gluster 3.4.2 on Redhat 6.5 I’ve got to the bottom of it…. By running glusterd in foreground with debug enabled I was able to see two error messages when the command was being run… it appears that it was requiring the xfsprogs package which I did not have installed. Once I installed it it appears that zombie processes are no longer being “created”.
REVIEW: http://review.gluster.org/7349 (glusterfs.spec.in: glusterd requires e2fsprogs and xfsprogs) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/7349 (glusterfs.spec.in: glusterd requires e2fsprogs and xfsprogs) posted (#2) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/7360 (glusterd: call runner_end even if runner_start fails) posted (#1) for review on master by Jeff Darcy (jdarcy)
REVIEW: http://review.gluster.org/7361 (xlators/mgmt: don't leave zombies if required programs aren't installed) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
*** Bug 1081605 has been marked as a duplicate of this bug. ***
REVIEW: http://review.gluster.org/7361 (xlators/mgmt: don't leave zombies if required programs aren't installed) posted (#2) for review on master by Kaleb KEITHLEY (kkeithle)
COMMIT: http://review.gluster.org/7360 committed in master by Anand Avati (avati) ------ commit aa199093fdf37dcd87a73cea83f9b9164d5800c5 Author: Jeff Darcy <jdarcy> Date: Thu Mar 27 18:51:08 2014 +0000 glusterd: call runner_end even if runner_start fails Change-Id: I5eca01a131307ba3be2aed4922eea73025ff284c BUG: 1081013 Signed-off-by: Jeff Darcy <jdarcy> Reviewed-on: http://review.gluster.org/7360 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Krishnan Parthasarathi <kparthas> Reviewed-by: Anand Avati <avati>
REVIEW: http://review.gluster.org/7361 (xlators/mgmt: don't leave zombies if required programs aren't installed) posted (#3) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/7361 (xlators/mgmt: don't leave zombies if required programs aren't installed) posted (#4) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/7361 (xlators/mgmt: don't leave zombies if required programs aren't installed) posted (#5) for review on master by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8134 (xlators/mgmt: don't allow glusterd fork bomb (cache the brick inode size)) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/8134 (xlators/mgmt: don't allow glusterd fork bomb (cache the brick inode size)) posted (#2) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/8134 (xlators/mgmt: don't allow glusterd fork bomb (cache the brick inode size)) posted (#3) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/8134 (xlators/mgmt: don't allow glusterd fork bomb (cache the brick inode size)) posted (#4) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/8134 (xlators/mgmt: don't allow glusterd fork bomb (cache the brick inode size)) posted (#5) for review on master by Kaleb KEITHLEY (kkeithle)
COMMIT: http://review.gluster.org/8134 committed in master by Krishnan Parthasarathi (kparthas) ------ commit f20d0ef8ad7d2f65a9234fc11101830873a9f6ab Author: Kaleb S. KEITHLEY <kkeithle> Date: Fri Jun 20 08:40:47 2014 -0400 xlators/mgmt: don't allow glusterd fork bomb (cache the brick inode size) Was don't leave zombies if required programs aren't installed Also, the existing if (strcmp (foo, bar) == 0) antipattern leaves me underwhelmed -- table driven is better; I like fully qualified paths to system tools too. File systems aren't going to change their inode size. Rather than fork-and-exec a tool repeatedly, hang on to the answer for subsequent use. Even if there are hundreds of volumes the size of a dict to keep this in memory is small. Change-Id: I704a8b1215446488b6e9e051a3e031af21b37adb BUG: 1081013 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: http://review.gluster.org/8134 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users