Project

General

Profile

Actions

Feature #41182

closed

mgr/volumes: add `fs subvolume extend/shrink` commands

Added by Ramana Raja over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
nautilus
Reviewed:
Affected Versions:
Component(FS):
mgr/volumes
Labels (FS):
Pull request ID:

Description

To extend and shrink subvolume set desired quota.

And during shrink, maybe error out if the desired shrunk size is greater than the used size of the subvolume.

Also, write appropriate tests to check whether the new quotas are enforced even with on-going I/Os on the subvolume.


Related issues 1 (0 open1 closed)

Copied to CephFS - Backport #42615: nautilus: mgr/volumes: add `fs subvolume extend/shrink` commandsResolvedJos CollinActions
Actions #1

Updated by Patrick Donnelly over 4 years ago

  • Assignee changed from Ramana Raja to Jos Collin
  • Start date deleted (08/09/2019)
Actions #2

Updated by Ramana Raja over 4 years ago

  • Status changed from New to In Progress
  • Priority changed from Normal to High
Actions #3

Updated by Jos Collin over 4 years ago

  • Pull request ID set to 30054
Actions #4

Updated by Jos Collin over 4 years ago

  • Status changed from In Progress to Fix Under Review
Actions #5

Updated by Patrick Donnelly over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #7

Updated by Jos Collin over 4 years ago

  • Status changed from Pending Backport to In Progress
Actions #8

Updated by Nathan Cutler over 4 years ago

  • Backport deleted (nautilus)
Actions #9

Updated by Nathan Cutler over 4 years ago

  • Status changed from In Progress to Pending Backport
  • Backport set to nautilus
Actions #10

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #42615: nautilus: mgr/volumes: add `fs subvolume extend/shrink` commands added
Actions #11

Updated by Nathan Cutler over 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF