Skip to content
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

Wip 6332 #606

Merged
merged 4 commits into from Sep 26, 2013
Merged

Wip 6332 #606

merged 4 commits into from Sep 26, 2013

Conversation

gregsfortytwo
Copy link
Member

This branch does two things:

  1. Requires users to run a "ceph mds allow_snaps --yes-i-really-mean-it" command before creating any (more) snapshots.
  2. Switches the MMonCommands --yes-i-really-mean-it commands to req=false so users have the chance to see the monitor warning output on those commands.

Sage Weil and others added 4 commits September 25, 2013 17:08
The current LOOKUPSNAP code path was dereferencing mdr->dn[0] and getting
SEGV.  Instead, set the do_lookup arg to false for getattr so that we do
not try to dereference this; for snaps it will always be NULL as we are
constructing a fake namespace for the .snap directory.  (This happens in
the path_traverse, the result of which is to set snapid--without any real
dentry).

With this fix, snaptest-0.sh passes.

Signed-off-by: Sage Weil <sage@inktank.com>
Reviewed-by: Greg Farnum <greg@inktank.com>
This way users can't put snapshots on their clusters unless they explicitly
ask for them and have seen a warning message. We take a bit of the MDSMap
flags in order to do so. The only thing a little weird here is that anybody
who upgrades to this patch who already has snapshots will hit the EPERM
and have to go through the warning, but it doesn't impact existing snapshots
at all so they should be good.

To go along with this, we add "ever_allowed_snaps" and "explicitly_allowed_snaps"
members to the MDSMap, which are default to false and are set to true
when allow_new_snaps is set. Old maps decoded with new code default to true
and false, respectively, so we can tell.

Fixes: #6332

Signed-off-by: Greg Farnum <greg@inktank.com>
Signed-off-by: Loic Dachary <loic@dachary.org>
Test that it works in snaptest-0.sh, and set the flag in
all the snap workunits so they continue to function.

Signed-off-by: Greg Farnum <greg@inktank.com>
Reviewed-by: Loic Dachary <loic@dachary.org>
By default options are required, and that leads to the Ceph CLI making
users add this to their commands before even submitting it to the monitor. We
want them to see and think about the messages generated by the monitor!

Signed-off-by: Greg Farnum <greg@inktank.com>
Signed-off-by: Loic Dachary <loic@dachary.org>
gregsfortytwo added a commit that referenced this pull request Sep 26, 2013
Reviewed-by: Sage Weil <sage@inktank.com>
@gregsfortytwo gregsfortytwo merged commit 881309d into master Sep 26, 2013
@gregsfortytwo gregsfortytwo deleted the wip-6332 branch September 26, 2013 17:30
liewegas pushed a commit to liewegas/ceph that referenced this pull request Nov 18, 2016
tasks/ceph_fuse.py: virtual machines need flexible mount timeout
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant