Red Hat Bugzilla – Bug 1295520
Manual mount command in S29CTDBsetup script lacks options (_netdev ...)
Last modified: 2016-06-16 09:53:22 EDT
Description of problem:
The manual mount command in the S29CTDBSetup.sh start script does not yield the same result as the created fstab entry. Specifically, the options _netdev,defaults,transport=tcp are missing.
The effects should be the same.
REVIEW: http://review.gluster.org/13170 (hook-scripts: reconsile mount, fixing manual mount) posted (#1) for review on master by Michael Adam (email@example.com)
REVIEW: http://review.gluster.org/13170 (hook-scripts: clean up and fix mount commands and options) posted (#2) for review on master by Michael Adam (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/13170 (hook-scripts: S29CTDBsetup: clean and fix mount commands and options) posted (#3) for review on master by Michael Adam (email@example.com)
COMMIT: http://review.gluster.org/13170 committed in master by Niels de Vos (firstname.lastname@example.org)
Author: Michael Adam <email@example.com>
Date: Mon Jan 4 18:50:38 2016 +0100
hook-scripts: S29CTDBsetup: clean and fix mount commands and options
This refactors the mount options of S29CTDBstart.sh into one
variable, removing the superfluous mentioning of 'default'.
The manual mount command is fixed to:
- also use the common options, thereby adding
(while this does not have an effect for the _netdev
option, it makes a difference for the transport option),
- also use the HOSTNAME variable just like the fstab entry,
- use a "/" in the remote location specification.
Hence it now behaves identically to the fstab mount.
Signed-off-by: Michael Adam <firstname.lastname@example.org>
Tested-by: Raghavendra Talur <email@example.com>
Reviewed-by: Raghavendra Talur <firstname.lastname@example.org>
Reviewed-by: Rajesh Joseph <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Niels de Vos <email@example.com>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
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.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.