Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

freenas-api-nfs seems to require minimum pvc of 1GiB?

See original GitHub issue

When using the new freenas-api-nfs driver trying to create a PVC of size 128Mi, I get an error that the minimum size is 1GiB. This did not seem to occur using the older driver with SSH.

pvc.yaml

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-homer
  namespace: default
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: "csi-truenas-nfs"
  resources:
    requests:
      storage: 128Mi

Excerpt from kubectl describe pvc:

Warning  ProvisioningFailed    104s (x8 over 3m50s)  org.democratic-csi.truenas-nfs_k-work-03_31cd949d-72c8-43f3-aac0-cb7da97eb4a5  failed to provision volume with StorageClass "csi-truenas-nfs": rpc error: code = Internal desc = Error: {"pool_dataset_update.refquota":[{"message":"Should be greater or equal than 1073741824 or Should be 0","errno":22}]}

Issue Analytics

State:
Created 2 years ago
Comments:19 (11 by maintainers)

Top GitHub Comments

1reaction

ahgrabercommented, Sep 16, 2021

Thanks for the follow up, and sorry for double-barrel-ing the issue

1reaction

travisghansencommented, Sep 7, 2021

It is a new limitation actually. I asked about it but never got an answer. Let me ask again.

Top Results From Across the Web

(cli): `--notification-arns` not validated - Aws/Aws-Cdk - IssueHint

freenas-api-nfs seems to require minimum pvc of 1GiB ? 19, 2021-09-07, 2022-10-20 ; Unbind metrics that are no longer relevant, 2, 2021-02-09, 2022-10-05....