-
Notifications
You must be signed in to change notification settings - Fork 76
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
LINSTOR creates volumes larger than requested size #421
Comments
In LINSTOR the volumes have different
Is it possible to order volumes in LINSTOR using usable_size, not allocated_size? |
I just tried to use |
Is there ant reliable way to request LINSTOR create a DRBD volume with exact size |
Correct me if I'm wrong, but reading the linked issue it does not look like the question / request here is that LINSTOR should not give you a little bit more space, but exactly the space you asked for, right? If so, please compare the sizes from Getting back to your example, if you ask LINSTOR for a 1GiB large volume (i.e. Am I missing something or is the title of this issue the wrong way around? |
Hi @ghernadi thank you for investigating, but seems I was wrong here, here is my pvc: apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: prime-dbabbeef-a3f4-412e-aec6-cdbc8acd2c05
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: "1073741824"
storageClassName: replicated
volumeMode: Block
volumeName: pvc-5b902b3e-24ef-431d-afdd-0746414a3e1a
For DRBD layer it is:
It seems CDI issue, I will continue investigating, and let you know. |
It seems there is a bug (or feature?) in CDI. It expects that volume will have exact size that requested in PVC. Personally I don't see the problem if the drive will be a n I didn't dig so far, but I see a potential issue, if CDI creates a new PVC with the same size as origin (and it reads this size from the PVC spec), but in fact that origin have larger volume inside it might block copying operations. |
I think LINSTOR should create drives with exact requested size from PVC, if it is not possible due to technical limitations, it should at least report correct usable_size into created PV after the volume is created |
I create PersistentVolumeClaim with size of
1Gi
:1Gi*1024*1024*1024
=1073741824
bytesBut inside the pod the size of volume is only
1073750016
:link kubevirt/containerized-data-importer#3159
The text was updated successfully, but these errors were encountered: