4.0.18 S3 storage namespace issues

PikachuEXE

New Member
Oct 25, 2025
2
0
1
Great to see S3 compatible storage support
I only starts using PBS recently
So far so good on using local storage

However I tried out S3 datastore and found out there is namespace (I was using root namespace on local too, switched just today...
But I found a few issues which makes it unusable with S3 + namespace (trying with backblaze, so that might or might not matter)

1. Cannot see list of namespaces (even though on bucket itself the folders and files are created)
2. No way to query backups if storage added with namespace (error message would be "create storage failed: storage-name: error fetching datastores - 401 Unauthorized (500)"

I did not try creating backup since the above failed

If there is anything else I can help understand & fix the issue please let me know thx

Update 1: 2nd one might be me editing /etc/pve/storage.cfg directly...
 
Last edited:
1. Cannot see list of namespaces (even though on bucket itself the folders and files are created)
Not seeing that issue here, namespaces are created as expected and can be listed in the PBS UI. Where do you fail to list the namespaces?
 
My steps:
- Add Namespace(s) (nested namespace not required)
- Press More -> Reload contents from S3 bucket (required to reproduce the issue)
- No any namespace shown (existing one is gone

Update 1: I added a backup to namespace and now only the namespaces with backups are loaded
However when a namespace is created a `.namespace` file is put inside the folder so it seems S3 side is ignoring folders without backups incorrectly
 
Last edited:
A few things:

- I have no issues with namespace on S3
- Reload contents only works when the datastore is in maintenance, otherwise you get weird things, so set it in maintenance, then reload contents, then take it out of mainantence
- Also, on the S3 itself check the ownership of the namespaces, does that user have access rights?

I'm not an expert, just mention things from the top of my head.

Good luck