Project

General

Profile

Bug #47515

pybind/snap_schedule: deactivating a schedule is ineffective

Added by Venky Shankar over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Correctness/Safety
Target version:
-
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Deactivating a snap schedule does not have any effect on the schedule. Schedules snapshots still get created by the snap-schedule module.

  1. ceph fs snap-schedule add /d1 1M fs=a
  2. ls /mnt/cephfs/d1/.snap
    scheduled-2020-09-17-12_40_00
  3. ceph fs snap-schedule deactivate /d1 1M fs=a
  4. ls /mnt/cephfs/d1/.snap
    scheduled-2020-09-17-12_40_00 scheduled-2020-09-17-12_41_00
  5. sleep 60
  6. ls /mnt/cephfs/d1/.snap
    scheduled-2020-09-17-12_40_00 scheduled-2020-09-17-12_41_00 scheduled-2020-09-17-12_42_00

(note: forcefully allowed minute granularity snaps for this. PR https://github.com/ceph/ceph/pull/34552 will allow config option to enable that).

History

#1 Updated by Venky Shankar over 3 years ago

(formatting fix)


ceph fs snap-schedule add /d1 1M fs=a
ls /mnt/cephfs/d1/.snap
scheduled-2020-09-17-12_40_00
ceph fs snap-schedule deactivate /d1 1M fs=a
ls /mnt/cephfs/d1/.snap
scheduled-2020-09-17-12_40_00 scheduled-2020-09-17-12_41_00
sleep 60
ls /mnt/cephfs/d1/.snap
scheduled-2020-09-17-12_40_00 scheduled-2020-09-17-12_41_00 scheduled-2020-09-17-12_42_00

#2 Updated by Venky Shankar over 3 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 37415

#3 Updated by Jan Fajerski over 3 years ago

  • Status changed from Fix Under Review to Resolved

Also available in: Atom PDF