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

quota is not set for the cloned volume in case of zfs file system #55

Closed
w3aman opened this issue Mar 10, 2020 · 1 comment · Fixed by #57
Closed

quota is not set for the cloned volume in case of zfs file system #55

w3aman opened this issue Mar 10, 2020 · 1 comment · Fixed by #57
Assignees

Comments

@w3aman
Copy link
Contributor

w3aman commented Mar 10, 2020

what happened:
Deploy application with pvc of 2Gi. After exec into the application if we do df -h we see the correct claimsize on mount point.

Filesystem                                          Size  Used Avail Use% Mounted on
overlay                                              98G  9.3G   84G  10% /
tmpfs                                                64M     0   64M   0% /dev
tmpfs                                               3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sda1                                            98G  9.3G   84G  10% /etc/hosts
shm                                                  64M     0   64M   0% /dev/shm
test-pool/pvc-6c79f1f9-dc91-408e-b0e1-aa9120dae6b3  2.0G  215M  1.8G  11% /var/lib/mysql
tmpfs                                               3.9G   12K  3.9G   1% /run/secrets/kubernetes.io/serviceaccount
tmpfs                                               3.9G     0  3.9G   0% /proc/acpi
tmpfs                                               3.9G     0  3.9G   0% /proc/scsi
tmpfs                                               3.9G     0  3.9G   0% /sys/firmware

But when tried to clone the volume and used it, exec into application show df -h as some different size which is not the clone volume size. In my case it is showing the zpool capacity.

root@percona1-7c776f8558-6cskw:/# df -h
Filesystem                                          Size  Used Avail Use% Mounted on
overlay                                              98G  9.3G   84G  10% /
tmpfs                                                64M     0   64M   0% /dev
tmpfs                                               3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sda1                                            98G  9.3G   84G  10% /etc/hosts
shm                                                  64M     0   64M   0% /dev/shm
test-pool/pvc-fe8c7583-9896-4ae8-9e59-0393f0858279  9.7G  215M  9.4G   3% /var/lib/mysql
tmpfs                                               3.9G   12K  3.9G   1% /run/secrets/kubernetes.io/serviceaccount
tmpfs                                               3.9G     0  3.9G   0% /proc/acpi
tmpfs                                               3.9G     0  3.9G   0% /proc/scsi
tmpfs                                               3.9G     0  3.9G   0% /sys/firmware

Note that:
This above scenario is with only zfs file system. Didn't see any size mismatch with ext4/xfs file system

@w3aman
Copy link
Contributor Author

w3aman commented Mar 13, 2020

After using the image for zfs-driver as quay.io/openebs/zfs-driver:v0.5.0-RC2 and onwards didn't hit this issue with zfs-file system.
Performed the same process as above and confirmed that size at mountpoint in case for original pvc and cloned pvc was equal.
Thanks !! @pawanpraka1

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

Successfully merging a pull request may close this issue.

2 participants