You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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.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.Note that:
This above scenario is with only zfs file system. Didn't see any size mismatch with ext4/xfs file system
The text was updated successfully, but these errors were encountered: