-
Notifications
You must be signed in to change notification settings - Fork 554
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
Do snapshots freeze fs before snapshotting ? #1532
Comments
Yes, it's the user's responsibility to make sure PVC is not in use before taking snapshots or creating the clone. Hope in feature, kubernetes will add a hook to do options to freeze the IO when we are taking snapshots or clone |
Thanks ! |
Yes please, @facchettos is it possible to send PR to update the doc? |
I'm on it =) |
@facchettos true , volume should not be in use while snapshot is taken, this has been mentioned as a prerequisties in kube. However there is no enforcement happening from the controller . Also refer kubernetes-csi/external-provisioner#437 |
Right, so the bigger point in the end is that ceph’s snapshots recommend
the volume not to be in use while taking the snapshot ? (
https://docs.ceph.com/en/latest/rbd/rbd-snapshot/ )
|
correct, also ceph as a storage provider offers crash consistent snapshots. |
What new functionality do you want?
Just some doc update, I could not find anywhere in the docs, whether or not when you create a snapshot the fs/block is frozen or not before the snapshot is taken. In the alpha description of volume snapshots (kubernetes), they talked about having to get the fs/bd into a frozen state before doing the snapshot but it disappeared in beta. I wonder if cephcsi does that or if someone that create snapshots should first make sure that the volumes are not in use before doing the snapshot ?
The text was updated successfully, but these errors were encountered: