Project

General

Profile

Actions
Copy link

Bug #45398

closed

mgr/volumes: Not able to resize cephfs subvolume with ceph fs subvolume create command

Added by Madhu Rajanna almost 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Kotresh Hiremath Ravishankar
Category:
-
Target version:
Ceph - v16.0.0
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
octopus,nautilus
Regression:
Yes
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
mgr/volumes
Labels (FS):
Pull request ID:
35090
Crash signature (v1):
Crash signature (v2):

Description

in cephcsi we are using ceph fs subvolume create command to resize the PVC, which is not working in the cluster which is higher version that 14.2.8.

i tried with ceph 15.2.1 here is the los

  • create PVC and mount it to app pod and check the size
sh-4.4# getfattr -n ceph.quota.max_bytes /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-e98c8e69-c187-4200-bb99-25ac53c3fd7c/globalmount
getfattr: Removing leading '/' from absolute path names
  1. file: var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-e98c8e69-c187-4200-bb99-25ac53c3fd7c/globalmount
    ceph.quota.max_bytes="1073741824
  • change the size with ceph fs subvolume create command and check the size
    sh-4.2# #ceph fs subvolume create myfs csi-vol-7e9c4973-8f8a-11ea-8cb2-0242ac110010 2147483648 --group_name csi
    sh-4.4# getfattr -n ceph.quota.max_bytes /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-e98c8e69-c187-4200-bb99-25ac53c3fd7c/globalmount
    getfattr: Removing leading '/' from absolute path names
    1. file: var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-e98c8e69-c187-4200-bb99-25ac53c3fd7c/globalmount
      ceph.quota.max_bytes="1073741824"
  • do the resize with resize command and check the size
    sh-4.2# ceph fs subvolume resize myfs csi-vol-7e9c4973-8f8a-11ea-8cb2-0242ac110010 2147483648 --group_name csi
    [ {
    "bytes_used": 0
    }, {
    "bytes_quota": 2147483648
    }, {
    "bytes_pcent": "0.00"
    }
    ]
sh-4.4# getfattr -n ceph.quota.max_bytes /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-e98c8e69-c187-4200-bb99-25ac53c3fd7c/globalmount
getfattr: Removing leading '/' from absolute path names
  1. file: var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-e98c8e69-c187-4200-bb99-25ac53c3fd7c/globalmount
    ceph.quota.max_bytes="2147483648"

more info at https://github.com/ceph/ceph-csi/issues/1002

Related issues 2 (0 open — 2 closed)

Copied to CephFS - Backport #45680: octopus: mgr/volumes: Not able to resize cephfs subvolume with ceph fs subvolume create commandResolvedWei-Chung ChengActions
Copied to CephFS - Backport #45681: nautilus: mgr/volumes: Not able to resize cephfs subvolume with ceph fs subvolume create commandResolvedRamana RajaActions
Actions
Copy link
 #1

Updated by Jos Collin almost 4 years ago

  • Subject changed from Not able to resize cephfs subvolume with ceph fs subvolume create command to mgr/volumes: Not able to resize cephfs subvolume with ceph fs subvolume create command
  • Component(FS) mgr/volumes added
Actions
Copy link
 #2

Updated by Patrick Donnelly almost 4 years ago

  • Assignee set to Kotresh Hiremath Ravishankar
  • Target version changed from v15.2.1 to v16.0.0
  • Backport set to octopus,nautilus
  • ceph-qa-suite deleted (fs)
Actions
Copy link
 #3

Updated by Kotresh Hiremath Ravishankar almost 4 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 35090
Actions
Copy link
 #4

Updated by Patrick Donnelly almost 4 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Source set to Community (dev)
Actions
Copy link
 #5

Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #45680: octopus: mgr/volumes: Not able to resize cephfs subvolume with ceph fs subvolume create command added
Actions
Copy link
 #6

Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #45681: nautilus: mgr/volumes: Not able to resize cephfs subvolume with ceph fs subvolume create command added
Actions
Copy link
 #7

Updated by Nathan Cutler almost 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
Copy link

Also available in: Atom PDF