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
s3cmd --access_key="981YUOTAZG8BMUMUNMQ1" --secret_key="QKdZWnXzb36M4fVA8slJnO6aSmb5csFm2DjcJasv" put kube-1.23.4-amd64.tar.gz s3://hengshibucket
upload: 'kube-1.23.4-amd64.tar.gz' -> 's3://hengshibucket/kube-1.23.4-amd64.tar.gz' [part 1 of 44, 15MB] [1 of 1]
1507328 of 15728640 9% in 0s 26.65 MB/s failed
1507328 of 15728640 9% in 0s 26.21 MB/s done
ERROR:
Upload of 'kube-1.23.4-amd64.tar.gz' part 1 failed. Use
/usr/bin/s3cmd abortmp s3://hengshibucket/kube-1.23.4-amd64.tar.gz 2~NdLSs4TWdctL60iPAkhM4Vzj8mR0e3r
to abort the upload, or
/usr/bin/s3cmd --upload-id 2~NdLSs4TWdctL60iPAkhM4Vzj8mR0e3r put ...
to continue the upload.
ERROR: S3 error: 403 (QuotaExceeded)
Try to make the pod mount this bucket to see if it can be restricted
Hi!
What's your question? Are you asking why the write operation hangs when it's over quota?
GeeseFS retries most upload errors (including quota errors) infinitely to give a chance to increase the quota, recover the mount and not lose any changes.
Description
对于限额的配置目前没有支持,只能通过自身去实现限制配额的大小
#59
I tried to do this using ceph's resource quotas, but encountered a stuck pod mount, here is my example
BUG REPORT
Versions
kubeadm version (use
kubeadm version
):v1.23.4
Environment:
kubectl version
):v1.23.4
vsphere
-** ceph version** (use
ceph -v
):ceph version 14.2.22 (ca74598065096e6fcbd8433c8779a2be0c889351) nautilus (stable)
uname -a
):1、Create a user
3.Verify buckets under a specific user
4、Set user quotas
5、Start the user quota
9、 Update quota statistics
Create pvc and specify a new bucket
create pod
Because the limit is set, it is stuck here and no error will be reported
Error information exists in csi-s3 logs
When I created pvc, but ceph doesn't seem to go far enough to see the creation of pvc
Is there something wrong with the above error message?
The text was updated successfully, but these errors were encountered: