-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refreshes to gluster::mount fail to remount the volume #10
Comments
skpy
pushed a commit
that referenced
this issue
Jan 23, 2015
As identified in #10, a refresh of a volume will attempt to remount the volume but the FUSE client does not support this. Set [remounts](https://docs.puppetlabs.com/references/3.4.stable/type.html#mount-attribute-remounts) to `false` on the mount resource. This means that any resource changes will cause the mount to be ***unmounted** and then mounted.
Great! Thanks all your hard work on this module, it's much appreciated! |
cegeka-jenkins
pushed a commit
to cegeka/puppet-gluster
that referenced
this issue
Jul 20, 2018
As identified in voxpupuli#10, a refresh of a volume will attempt to remount the volume but the FUSE client does not support this. Set [remounts](https://docs.puppetlabs.com/references/3.4.stable/type.html#mount-attribute-remounts) to `false` on the mount resource. This means that any resource changes will cause the mount to be ***unmounted** and then mounted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
if a refresh is triggered on a gluster::mount, puppet attempts to remount the filesystem with
mount -o remount
. This results an error like:...because gluster FUSE mounts don't support that option.
I propose passing the
remounts => false
option to themount
directive in thegluster::mount
class to avoid this behaviour.The text was updated successfully, but these errors were encountered: