Closed gproxyz closed 1 year ago
Just restart node-server
pod on the node.
@balamurugana
Just restart
node-server
pod on the node.
This is first what I am doing. But Its doesn't help
kubectl rollout restart daemonset node-serve
kubectl directpv list drives
Show old size: 100Gb.
┌─────────┬──────┬────────────────────┬─────────┬────────┬─────────┬────────┐
│ NODE │ NAME │ MAKE │ SIZE │ FREE │ VOLUMES │ STATUS │
├─────────┼──────┼────────────────────┼─────────┼────────┼─────────┼────────┤
│ server1 │ sdb │ QEMU QEMU_HARDDISK │ 100 GiB │ 25 GiB │ 1 │ Ready │
│ server1 │ sdc │ QEMU QEMU_HARDDISK │ 100 GiB │ 25 GiB │ 1 │ Ready │
│ server1 │ sdf │ QEMU QEMU_HARDDISK │ 100 GiB │ 25 GiB │ 1 │ Ready │
│ server1 │ sdg │ QEMU QEMU_HARDDISK │ 100 GiB │ 25 GiB │ 1 │ Ready │
directpv version v4.0.4
@gproxyz If you did xfs_growfs
and node-server
pod restart, but still see crd is not updated, just manually edit it and move forward. As DirectPV
is meant for DAS
and real drives, it is fine ATM. I will test it locally before confirming this issue.
we currently do not support xfs resizing of initialized drives @balamurugana
this is because, we probe the size from xfs superblock which here is reflecting the older size.
@Praveenrajmani Actually I tested this by adding 512MiB disk first, then resized to block level to 1.5GiB, then xfs_growfs /var/lib/directpv/mnt/<FSUUID>
and finally restarted daemonset. It works pretty fine.
Sorry for the long answer.
@balamurugana
In my case, after rebooting the OS
kubectl directpv list drives
shows new size
Perhaps this is because the OS is CentOS 7
But now everything is working fine.
Thank you.
@balamurugana Hi
Can you please write the commands you executed? Because I'm trying to do the same thing again and I'm not getting the disk size updated to the new values.
Here is what I did:
/dev/sdc
disksudo xfs_growfs /var/lib/directpv/directpv/mnt/<FSUUID>
.kubectl -n directpv delete pod/node-server-<id>
.
kubectl directpv list drives --output wide
-- old value there.sudo systemctl daemon-reload
.
sudo systemctl restart snap.microk8s.daemon-kubelite.service
.
kubectl rollout restart -n directpv daemonset node-server
.
If I restart the node after step 3, then it has the correct value, not the old one, but I would like to see if it is possible to bypass it without restarting the whole node.
P.s. I apologize if this request seems silly to you, I'm just learning all this stuff.
@Keonik1
node-server
pod on the node. If your system doesn't show increased size after node-server
restart, restart the node.
Hi, I manually resized disk and extend filesystem. Now disk is 101G
New size returned by
kubectl get directpvnodes.directpv.min.io -o yaml
But CRD
directpvdrives.directpv.min.io
showed old sizekubectl get directpvdrives.directpv.min.io f74ec73f-e82e-4b44-9b3b-334c9cb09d7f -o yaml
How to resize directpvdrive?