Bug 1199545
| Summary: | mount.glusterfs uses /dev/stderr and fails if the device does not exist | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | nico-redhat-bugzilla | |
| Component: | scripts | Assignee: | nico-redhat-bugzilla | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | mainline | CC: | bugs, gluster-bugs, ndevos | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.7.0 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1199577 (view as bug list) | Environment: | ||
| Last Closed: | 2015-05-14 17:29:18 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1199577 | |||
REVIEW: http://review.gluster.org/9824 (Replace /dev/stderr with >&2 in mount scripts) posted (#1) for review on master by Nico Schottelius (nico-gluster-users) I'll move this to the master branch, and will clone the bug to get the fix backported to release-3.6. COMMIT: http://review.gluster.org/9824 committed in master by Vijay Bellur (vbellur) ------ commit adef0c8860f57c8137382d848244009e9a584497 Author: Nico Schottelius <nico.org> Date: Fri Mar 6 16:25:33 2015 +0100 Replace /dev/stderr with >&2 in mount scripts /dev/stderr is not available on boot in CentOS 7 and thus mounting anything from /etc/fstab at boot time fails. Instead of using /dev/stderr, the standard error redirection ">&2" is being used. Change-Id: I15d07cd49e6b0392331047edb441925f48047b2b BUG: 1199545 Signed-off-by: Nico Schottelius <nico.org> Reviewed-on: http://review.gluster.org/9824 Reviewed-by: Niels de Vos <ndevos> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra Talur <rtalur> 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.0, please open a new bug report. glusterfs-3.7.0 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] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [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.0, please open a new bug report. glusterfs-3.7.0 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] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [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.0, please open a new bug report. glusterfs-3.7.0 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] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [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.0, please open a new bug report. glusterfs-3.7.0 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] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |
Description of problem: Instead of using standard >&2 implementation, mount.glusterfs writes to /dev/stderr. This causes the mount to fail on current CentOS 7 systems with the following message: Mar 06 16:13:44 entrance mount[1886]: /sbin/mount.glusterfs: line 13: /dev/stderr: No such device or address Version-Release number of selected component (if applicable): 3.6.2 How reproducible: always Steps to Reproduce: 1. Add entry to /etc/fstab on CentOS 7 with glusterfs 3.6.2, reboot. 2. systemctl status Actual results: var-lib-one-datastores-100.mount - /var/lib/one/datastores/100 Loaded: loaded (/etc/fstab) Active: failed (Result: exit-code) since Fri 2015-03-06 16:13:44 CET; 42s ago Where: /var/lib/one/datastores/100 What: vmhost2-cluster1.place4.ungleich.ch:/cluster1 Process: 1886 ExecMount=/bin/mount vmhost2-cluster1.place4.ungleich.ch:/cluster1 /var/lib/one/datastores/100 -t glusterfs -o defaults,_netdev,backupvolfile-server=vmhost1-cluster1.place4.ungleich.ch (code=exited, status=1/FAILURE) Mar 06 16:13:40 entrance systemd[1]: Mounted /var/lib/one/datastores/100. Mar 06 16:13:44 entrance mount[1886]: /sbin/mount.glusterfs: line 13: /dev/stderr: No such device or address Mar 06 16:13:44 entrance systemd[1]: var-lib-one-datastores-100.mount mount process exited, code=exited status=1 Mar 06 16:13:44 entrance systemd[1]: Unit var-lib-one-datastores-100.mount entered failed state. [16:14:27] entrance:~# Expected results: glusterfs volumes mound Additional info: Preparing a patch for inclusion at the moment