Search results

Usually delay is corelated to slow disks, you didn't write all info about your platform. SSD type,etc,etc

1),yes it works okay,i would say with minimum of 5 ceph nodes 2) yes, different crush rules based on disk type.

apt-remove systemd-boot and that is it. After that i upgraded more than 5 machines with this error, and they all booted fine.

Hope he didn't charge you for the advice. Maybe he is disaster recovery consultant.

Ubuntu will probably go with 6.17 kernel, so this will be proxmox next one.

No, systemd is newer,nothing else in the grub.

Yes, i'm running with with newer systemd

Yeah but that is s3 client not server.

What is enhanced HBA mode? With 10gb, you are limited to around 1200MB/s , and that's it.

Maybe it is easier just to spin up lxc with bindmount to cephfs?

If you are using minio or garage for local hosted s3, they will probably always be slower than samba or nfs.

Yeah,if license(or atlest subscription expires) ends , everything works. This is OSS.

S3 only solves horizontal scaling better than smb or nfs.

Probably around June 2026.

As i said, one more problem is if you are hosting your own minio or garage or whatever , there isn't a region.

OKay finally got it: s3.cfg s3-endpoint: Wasabi access-key endpoint {{bucket}}.s3.{{region}}.wasabisys.com region ca-central-1 secret-key datastore.cfg datastore: Wasabi backend bucket=proxmox,client=Wasabi,type=s3 comment gc-schedule daily notification-mode...

Hm,this is the error for most of them: root@rrr:~# proxmox-backup-manager s3 check Wasabi proxmox --store-prefix test0 Error: head object failed Caused by: bucket does not exist or no permission to access it cat /etc/proxmox-backup/s3/cfg s3-endpoint: Wasabi access-key endpoint...

Another test,with ceph s3: failed to upload in-use marker for datastore: unexpected status code 404 Not Found ceph URL : https://storage.losproxmox.com:8089 AccessKey : SecretKey : API : s3v4 Path : auto Src : /root/.mc/config.json

If you are hosting S3,you usually don't even need region, so it should be an option variable in any case.

Usually i test with mc command , like mc alias: wasabi URL : https://ca-central-1.wasabisys.com AccessKey : SecretKey : API : s3v4 Path : auto Src : /root/.mc/config.json And this works