+++ This bug was initially created as a clone of Bug #1129939 +++ This bug is a placeholder to gather change sets for porting GlusterFS to NetBSD
REVIEW: http://review.gluster.org/10279 (Fix case mistake for MKDIR_P in Makefiles) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10287 (Tests: python portability) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10279 (Fix case mistake for MKDIR_P in Makefiles) posted (#2) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10287 (Tests: python portability) posted (#2) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10302 (Auto-retry failed tests to workaround spurious failures) posted (#2) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/10287 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 6f0e3981c29beca7d83695ad8f5ab521b129771b Author: Emmanuel Dreyfus <manu> Date: Sun Apr 19 03:11:39 2015 +0200 Tests: python portability Make sure to use $PYTHON defined from tests/env.rc so that we get the path to the actually detected python interpreter. Resubmit after rebase in hope that regression test will have less spurious failures. Backport of Ibf3e88f190d5e0c6a4a08e8d5ef9d0b5cba5078a BUG: 1212676 Change-Id: I0c39d1c64423c8c9b99f8abf8f8cd813ed6a0deb Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/10287 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
COMMIT: http://review.gluster.org/10279 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 8611fe7b30f86ddde5d5acfde45a6ec424186e02 Author: Emmanuel Dreyfus <manu> Date: Sun Apr 19 03:02:50 2015 +0200 Fix case mistake for MKDIR_P in Makefiles Some makefiles used $(mkdir_p) instead of the corectly defined $(MKDIR_P). The former is substituted as an empty string, leading to possible failures depending of the user shell tolerance. NetBSD's /bin/sh seems to choke more easily than Linux's /bin/bash, but if the later does not fail, it does not created the intended directories anyway. Resubmit after rebase in hope that regression test will have less spurious failures. Backport of: I8caed4000f3c91cb3a685453848fb854793945ed BUG: 1212676 Change-Id: I393ffda8aa24bffce86f7b1f19b999ffa30c3562 Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/10279 Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/10346 (Tests: trash.t portability fixes) posted (#1) for review on release-3.7 by Anoop C S (achiraya)
COMMIT: http://review.gluster.org/10302 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit ec7f11bfc315546313174f58fd43041846e8aa6f Author: Emmanuel Dreyfus <manu> Date: Thu Apr 23 05:10:59 2015 +0200 Auto-retry failed tests to workaround spurious failures Add a -r flag to run-tests.sh that will cause failed tests to be retried once. The idea is to reduce the impact of spurious failures: no need to retrigger in jenkins, and no need to replay all the tests. Backport of: I176bb32678835a669992fbac7de4dd14ee5c62bc If4e3c96d51037fbcf6d9d0e10a3dd3e12da77447 Resubmit since regression did not catch that one. BUG: 1212676 Change-Id: I31a1d71118bc9295d5c858dbf1e664d0f2aed6ff Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/10302 Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/10346 (Tests: trash.t portability fixes) posted (#2) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10374 (Tests: fix spurious failures in trash.t) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/10346 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 6bfd1e57e5fe4e94c6873054dc8636c98ac5691e Author: Emmanuel Dreyfus <manu> Date: Thu Apr 23 06:32:38 2015 +0200 Tests: trash.t portability fixes Backport of http://review.gluster.org/#/c/10327/ Fix various portability problems in trash.t - work around timing issues - avoid wildcard usage only supported by bash Original patch from Anoop C S and Jiffin Tony Thottan. Removed LONGER_HEAL_TIMEOUT from previous patch as it seems to run fine without it now. BUG: 1212676 Change-Id: I0f6f484209ef4db7e0a7b733b863927cb248e73e Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/10346 Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/10374 (Tests: fix spurious failures in trash.t) posted (#2) for review on release-3.7 by Vijay Bellur (vbellur)
COMMIT: http://review.gluster.org/10374 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit dfc84d7a7c08d0fb7b1d0bfb8f9dd33ea8285bf1 Author: Emmanuel Dreyfus <manu> Date: Sun Apr 26 05:29:19 2015 +0200 Tests: fix spurious failures in trash.t Fix timing problems that cause rare spurious failures in trash.t Backport of I673e033b53b6b4bb993c22fadbdcee725b2c1e96 BUG: 1212676 Change-Id: I319f94b7e099e189c08543da526d90d36318fe4b Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/10374 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/10395 (tier: fix off-by-one overrun in UUID string) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/10395 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit ed96153b8a2586ccf00885ed73836921e26e5837 Author: Emmanuel Dreyfus <manu> Date: Mon Apr 27 06:37:01 2015 +0200 tier: fix off-by-one overrun in UUID string UUID strings are UUID_CANONICAL_FORM_LEN (36) bytes long plus the trailing nul character that various function (e.g.: uuid_unparse) will add. As a consequence, UUID strings must be declared as UUID_CANONICAL_FORM_LEN+1 long, otherwise we get a off-by-one overrun that corrupts the next variable on stack. Backport of: I5837ad6ca06fa17cc7ab143eedd02d8099ecca2a BUG: 1212676 Change-Id: I27bd223bdd72cda679b7cdc861e09e0f367bd6e4 Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/10395 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig>
REVIEW: http://review.gluster.org/10408 (tier: relax libgfdb required version number) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10408 (tier: relax libgfdb required version number) posted (#2) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/10408 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 211b75e21e3f4a93307ae47b4fc9dc6cd3681394 Author: Emmanuel Dreyfus <manu> Date: Mon Apr 27 15:50:19 2015 +0200 tier: relax libgfdb required version number When calling dlopen() for libgfdb, do not specify the library version number "libgfdb.so.0.0.1", since libtool will not always create libraries or link with that name with the full 3-digit version. For instance on NetBSD only up to the 2-digit version is available and "libgfdb.so.0.0.1" does not exist. Instead, just specify "libgfdb.so" and rely on smymlinks installed by libtool to find the relevant library. Backport of: I074b1009d3622a122fdaeb4b99658bca3277e211 BUG: 1212676 Change-Id: I334cb6be8508051105c393ce4bb350f9df014df5 Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/10408 Reviewed-by: Dan Lambright <dlambrig> Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/10434 (tests: sync run-tests.sh from master) posted (#1) for review on release-3.7 by Vijay Bellur (vbellur)
COMMIT: http://review.gluster.org/10434 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 7e2baf9acda16cacf3410c22229889f362853384 Author: Vijay Bellur <vbellur> Date: Tue Apr 28 23:48:18 2015 +0530 tests: sync run-tests.sh from master A few commits going out of order for run-tests.sh between master and release-3.7 cause problems with cherrypicking patches for the file accepted on master. Since run-tests.sh does not contain any branch specific code, this change would be fine for release-3.7. Change-Id: I6da42a0a16293e108301f470a686c596dd70b82c BUG: 1212676 Signed-off-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/10434 Tested-by: NetBSD Build System Reviewed-by: Jeff Darcy <jdarcy> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/10587 (Tests: workaround NetBSD failures in cdc.t) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/10587 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 1fa8ac6655bdaf6fbebb27b3f5192d9c0491c6bd Author: Emmanuel Dreyfus <manu> Date: Tue May 5 17:02:22 2015 +0200 Tests: workaround NetBSD failures in cdc.t The volume reset network.compression operation cause brick processes to be restarted. If the volume is already started, a brick process is already there and the restart will fail, as the brick TCP port is already in use. Because the new brick process is not started, the volume is left with no brick online, and the volume stop operation will timeout waiting for bricks to stop. Obviosuly we have two bugs here - If volume reset network.compression needs to restart the bricks, it should first make sure the previous brick process is terminated - volume stop should not wait forever for bricks to come back online This change does not fix the bugs but just makes sure the volume is stoped before volume reset network.compression, so that the failure oes not happen. backport of: I9cd5cdc767ef6ee9dd31f2121d672dc3bfdce45f BUG: 1212676 Change-Id: If85c46f7ed675c4c84cc4170292b1f0f41e5b456 Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/10587 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/10648 (Tests: use a portable way to flush kernel cache) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10650 (glupy: fix tuntime search path and python module directory layo ut) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10653 (Restore build on non Linux systems) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/10653 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 6f8f47b6cbfbe96bc1324d836ed4baeab112a2f2 Author: Emmanuel Dreyfus <manu> Date: Thu May 7 20:36:24 2015 +0200 Restore build on non Linux systems This change broke the build on NetBSD, FreeBSD, and MacOS X: http://review.gluster.org/10526/ We restore the build with two fixes: - Use POSIX-compliant sysconf(_SC_NPROCESSORS_ONLN) to get the number of processors, instead of Linux specific get_nprocs(). That let us remove Linux-specific #include <sys/sysinfo.h> - Only define MAX() if it is not already defined. NetBSD defines it in <sys/param.h> which is already included Backport of: I62341c670598670e47ea2f69ab94864f96588b18 BUG: 1212676 Signed-off-by: Emmanuel Dreyfus <manu> Change-Id: I0f098153e76954bb85b5dca3f054a069e31dd94c Reviewed-on: http://review.gluster.org/10653 Reviewed-by: Shyamsundar Ranganathan <srangana> Reviewed-by: Kaleb KEITHLEY <kkeithle> Tested-by: Vijay Bellur <vbellur>
COMMIT: http://review.gluster.org/10648 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit d27ecba4f8b453a6d4f2466a5583a8360a068a14 Author: Emmanuel Dreyfus <manu> Date: Thu May 7 16:45:53 2015 +0200 Tests: use a portable way to flush kernel cache On Linux, kernel cache can be flushed using echo 3 > /proc/sys/vm/drop_caches This non-portable approach can be replaced by an on-purpose failed attempt to unmount: if the mount point is the current directory and umount is called, the kernel will flush inodes until it realize it cannot complete the operation because root of filesystem is busy: ( cd $M0 ; umount $M0 ) Unfortunately this does not flush everything. Entries may still be present in the kenrel FUSE cache. Using $GFS to mount the filesystem ensure --entry-timeout=0 and clears this problem. Some stall information may also remain in glusterfs caches, and that may have to be adressed by appropriate volume option. For instance tests/bugs/rpc/bug-954057.t needs to disable performance.stat-prefetch. Qtherwise, root's new credentials are not evaluated after root-quash is enabled. The test could also be done with performance.stat-prefetch enabled using various tricks: copying the file to read, creating a hard link on it, or just waiting long enough for metadata cache to expire. Backport of: I54929e899d55c04dcd9d947809133549f01fd0e1 BUG: 1212676 Signed-off-by: Emmanuel Dreyfus <manu> Change-Id: I2849a27acaa0334ef30aae3b852019b5a6eeb419 Reviewed-on: http://review.gluster.org/10648 Reviewed-by: Niels de Vos <ndevos> Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System
REVIEW: http://review.gluster.org/10658 (Tests: fix file count in ec-readdir.t) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10658 (Tests: fix file count in ec-readdir.t) posted (#2) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/10733 (glupy: remove debug test in libpython runtime search path detection) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/10733 committed in release-3.7 by Niels de Vos (ndevos) ------ commit 0c61a29a980a60a4555683ae2fea626ed3cb73e8 Author: Emmanuel Dreyfus <manu> Date: Sat May 9 21:09:43 2015 +0200 glupy: remove debug test in libpython runtime search path detection A configure test was recently added to add libpython runtime search path to glupy.so xlator. The vesion committed was a debug test, it searched pythonxx and not python to check for failure. Fix by removing the xx debug test in python's name. Backport of: I7b691be17fc2a2c812f68710869b1a9a85ced84c Change-Id: I518f369c320dcd5cddbdcfe9d25d27af2e0dc929 Signed-off-by: Emmanuel Dreyfus <manu> BUG: 1212676 Reviewed-on: http://review.gluster.org/10733 Reviewed-by: Niels de Vos <ndevos> Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/10749 (Tests: avoid hang in br-stub.t) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/10749 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 83777286f6ca1213509080ea8bcc43e8cd91db65 Author: Emmanuel Dreyfus <manu> Date: Mon May 11 03:35:06 2015 +0200 Tests: avoid hang in br-stub.t br-stub.t forgot to unmount the NFS mount, leading to the situation where cleanup code had to do it after glusterfs daemon were shut down. NetBSD has trouble dealing with this situation and may enter endless wait for the NFS server to come back. Fix is simply to unmount before the end og the script Backport of I972d379172a75f29ad11abc66d700c2d31106194 BUG: 1212676 Change-Id: I81b3823e71aca8d8e976da63d226c0be0d462b69 Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/10749 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaleb KEITHLEY <kkeithle> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/13205 (NetBSD regression reliability: properly cleanup loopback devices) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/13205 (NetBSD regression reliability: properly cleanup loopback devices) posted (#2) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/13247 (NetBSD regression reliability: retry non-bad tests) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/13247 (NetBSD regression reliability: retry non-bad tests) posted (#2) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/13205 (NetBSD regression reliability: properly cleanup loopback devices) posted (#3) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/13247 (NetBSD regression reliability: retry non-bad tests) posted (#3) for review on release-3.7 by Emmanuel Dreyfus (manu)
REVIEW: http://review.gluster.org/13205 (NetBSD regression reliability: properly cleanup loopback devices) posted (#4) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/13205 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit 57ca7c831cd231f56502d0aa5a4d042a48f5894e Author: Emmanuel Dreyfus <manu> Date: Mon Jan 18 20:53:22 2016 +0100 NetBSD regression reliability: properly cleanup loopback devices When a loopback device is configured and we forcibly unmount the filesystem containing the backing store, further vnconfig -l will complain "vnconfig: VNDIOCGET: Bad file descriptor" causing failures. We fix this by iterating on all loopback devices available in /dev, testing for this condition and manually unconfiguring when it happens. Backport of: I17b956a8ed28a7767f2d0dda83b93c523d3238c2 BUG: 1212676 Change-Id: I9d6fdd859572b653e1144c7d9d98a977cc3e255a Signed-off-by: Emmanuel Dreyfus <manu> Reviewed-on: http://review.gluster.org/13205 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu> CentOS-regression: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/13868 (Build fix: remove undefined -I${rpclibdir}) posted (#1) for review on release-3.7 by Emmanuel Dreyfus (manu)
COMMIT: http://review.gluster.org/13868 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit c3776dc86017e7a9139f5ef6f1ebb6f2e3027e4c Author: Emmanuel Dreyfus <manu> Date: Thu Mar 31 09:41:38 2016 +0200 Build fix: remove undefined -I${rpclibdir} The variable is not defined anywhere, remove it. Backport of Iaefb349cceb4108ac22c44cd32e5ea3d3c8bc0e5 Change-Id: I2ef75c8da8c7421328958f91dfaaf287347296e4 Signed-off-by: Emmanuel Dreyfus <manu> BUG: 1212676 Reviewed-on: http://review.gluster.org/13868 Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Vijay Bellur <vbellur>
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.7.7, please open a new bug report. glusterfs-3.7.7 has been announced on the Gluster mailinglists [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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
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.7.12, please open a new bug report. glusterfs-3.7.12 has been announced on the Gluster mailinglists [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] https://www.gluster.org/pipermail/gluster-devel/2016-June/049918.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user