No, unfortunately after a GC task the file is not created.
Yes, the 'backup' user is allowed to write via nfs to the nas/san.
The 'backup' user is the 1001 user as seen in the posts before.
It looks like if the file is not present, PBS won't create it.
Even if I create the .gc-status file...
There seem to be no .gc-status file in the datastore.
Only .lock and .chunks
I haven't manually adjusted anything, just installed PBS and upgraded over time.
Results from the prompt
root@proxpbs:/# cd mnt/backup-pbs/
root@proxpbs:/mnt/backup-pbs# ls -la
total 8279
drwxr-xr-x 5 1001 1001...
System running: PBS 2.2-1 / Linux proxpbs 5.15.35-1-pve #1 SMP PVE 5.15.35-3
Deduplication not correctly shown (storage in PBS is supplied via NFS).
After the garbage collect run has done it's work, it shows a deduplication factor of 11.61
But when you look the summary of the datastore, it...
In the documentation is a typo, not sure where to report, so put it here.
Just to help out to make the namespace documentation a little better.
https://pbs.proxmox.com/docs/terminology.html?highlight=namesapce
As you can see, namesapce should be namespace in that part.
Looks like mid 2022 has the first interesting server solution coming out which makes running Proxmox on Risc V an interesting option:
https://www.eetimes.com/sifive-unveils-64-bit-risc-v-server-core/
https://www.theregister.com/2021/12/02/sifive_p650_launch
Any reason for 'chrony' still showing up as an 'Unknown' and 'Dead' service in v7.0.8?
Bug? Special feature or easter-egg? Or legacy that still needs to be removed?
Can I do something about it or will it be solved in a new release?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.