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

[RFE]: how to expand the KadaluStorage size? #970

Open
jangrui opened this issue Mar 16, 2023 · 4 comments · May be fixed by #971
Open

[RFE]: how to expand the KadaluStorage size? #970

jangrui opened this issue Mar 16, 2023 · 4 comments · May be fixed by #971
Labels
on-dev pending on dev

Comments

@jangrui
Copy link

jangrui commented Mar 16, 2023

Is your feature request related to a problem? Please describe.

After expanding the host disk, how to expand the KadaluStorage size?

Describe the solution you'd like
Kadalu storage pool automatically expands when it detects a device size change.

Describe alternatives you've considered

Additional context
image
image

@jangrui jangrui changed the title [RFE]: KadaluStorage [RFE]: how to expand the KadaluStorage size? Mar 16, 2023
@aravindavk
Copy link
Member

Workaround: Login to server pods(server-kadalu-kadalu-{14,15,16}) and run xfs_growfs command.

xfs_growfs -d /bricks/kadalu/data/brick

@aravindavk
Copy link
Member

@vatsa287 while starting the server process (server/glusterfsd.py:create_and_mount_brick) we can run xfs_growfs command if the fs type is XFS.

@vatsa287
Copy link
Member

Should we take care that -d sets value greater than current value since xfs does not support shrinking of fs.?
Should a support for extending to a particular given size using -D be made?

vatsa287 added a commit to vatsa287/kadalu that referenced this issue Mar 21, 2023
Fixes: kadalu#970
Signed-off-by: Shree Vatsa N <[email protected]>
@vatsa287 vatsa287 linked a pull request Mar 21, 2023 that will close this issue
3 tasks
@leelavg leelavg added the on-dev pending on dev label Sep 15, 2023
@chadchiti
Copy link

hello guys. i did xfs_growfs -d /bricks/kadalu/data/brick and it worked. i can see the new size on servers and provisionner.
how to reflect the change in the operator pod?

root@operator-d8695df88-zdbfb:/# kubectl-kadalu storage-list --status

Name Type Utilization Pvs Count Min PV Size Avg PV Size Max PV Size
replica2-test Replica2 21 Gi/499 Gi (4%) 6 1 Gi 3 Gi 8 Gi
replica2 Replica2 48 Gi/99 Gi (48%) 43 1 Gi 1 Gi 5

root@kadalu-csi-provisioner-0:/# df -h
Filesystem Size Used Avail Use% Mounted on
overlay 59G 17G 40G 30% /
tmpfs 87G 0 87G 0% /sys/fs/cgroup
/dev/mapper/rootvg-var 59G 17G 40G 30% /plugin
devtmpfs 87G 0 87G 0% /dev
shm 64M 0 64M 0% /dev/shm
tmpfs 173G 0 173G 0% /etc/secret-volume
tmpfs 173G 12K 173G 1% /run/secrets/kubernetes.io/serviceaccount
kadalu:replica2 110G 3.5G 107G 4% /mnt/replica2
kadalu:replica2-test 500G 5.4G 495G 2% /mnt/replica2-test

root@server-replica2-0-0:/# df -h
Filesystem Size Used Avail Use% Mounted on
overlay 296G 132G 149G 47% /
devtmpfs 126G 0 126G 0% /dev
shm 64M 0 64M 0% /dev/shm
/dev/mapper/rootvg-var 296G 132G 149G 47% /etc/hosts
/dev/mapper/rootvg-usr 50G 6.1G 41G 14% /lib/modules
tmpfs 126G 0 126G 0% /sys/fs/cgroup
tmpfs 252G 12K 252G 1% /run/secrets/kubernetes.io/serviceaccount
/dev/mapper/mpathk 110G 2.4G 108G 3% /bricks/replica2/data

root@server-replica2-1-0:/# df -h
Filesystem Size Used Avail Use% Mounted on
overlay 296G 96G 185G 34% /
devtmpfs 126G 0 126G 0% /dev
shm 64M 0 64M 0% /dev/shm
/dev/mapper/rootvg-var 296G 96G 185G 34% /etc/hosts
/dev/mapper/rootvg-usr 50G 6.2G 41G 14% /lib/modules
tmpfs 126G 0 126G 0% /sys/fs/cgroup
tmpfs 252G 12K 252G 1% /run/secrets/kubernetes.io/serviceaccount
/dev/mapper/mpathm 110G 2.4G 108G 3% /bricks/replica2/data

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
on-dev pending on dev
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants