[SOLVED] Error creating datastore on NFS mount

So if the permissions on the datastore are fine, the error you are getting might rather be related to the privileges of the user you are trying to access the contents via the api with. Please check the ACLs for the user and/or its API token, if used.

What is the output of cat /etc/proxmox-backup/acl.cfg?
 
So this ih the response to the command:

root@pbs:~# cat /etc/proxmox-backup/acl.cfg
acl:1:/:remote_admin@pbs:RemoteAdmin
acl:1:/datastore:remote_admin@pbs:DatastoreBackup
acl:1:/datastore/NFS_Backup_Pointel:backup@pbs:DatastoreAdmin
acl:1:/datastore/NFS_Backups:backup@pbs:DatastoreAdmin
acl:1:/datastore/NFS_Backups:remote_admin@pbs:DatastoreReader
 
g.migliaccio said:
So this ih the response to the command:

root@pbs:~# cat /etc/proxmox-backup/acl.cfg
acl:1:/:remote_admin@pbs:RemoteAdmin
acl:1:/datastore:remote_admin@pbs:DatastoreBackup
acl:1:/datastore/NFS_Backup_Pointel:backup@pbs:DatastoreAdmin
acl:1:/datastore/NFS_Backups:backup@pbs:DatastoreAdmin
acl:1:/datastore/NFS_Backups:remote_admin@pbs:DatastoreReader
Click to expand...
Are you maybe accessing the datastore in PVE via the remote_admin@pbs user? As that is allowed to perform backups, but not to prune any contents.

Edit: But note that that should not have changed with the NFS share not being available! So the permissions might already have been set incorrectly or have been changed afterwards.
 
Last edited:
Chris said:
Edit: But note that that should not have changed with the NFS share not being available! So the permissions might already have been set incorrectly or have been changed afterwards.
Click to expand...

Ok I understand, i changed @remote permissions:

root@pbs:~# cat /etc/proxmox-backup/acl.cfg
acl:1:/:remote_admin@pbs:RemoteAdmin
acl:1:/datastore:remote_admin@pbs:DatastoreBackup
acl:1:/datastore/NFS_Backup_P:remote_admin@pbs:DatastoreAdmin

Please can you check the new response?
 
g.migliaccio said:
Ok I understand, i changed @remote permissions:

root@pbs:~# cat /etc/proxmox-backup/acl.cfg
acl:1:/:remote_admin@pbs:RemoteAdmin
acl:1:/datastore:remote_admin@pbs:DatastoreBackup
acl:1:/datastore/NFS_Backup_PNFS_Backup_P:remote_admin@pbs:DatastoreAdmin

Please can you check the new response?
Click to expand...
Well, that depends on what permissions you would like that user to have ;)
As is, you allow to perform remote config administration, creation and restore of owned backups on all datastores but only administration of the datastore NFS_Backup_PNFS_Backup_P. Please check the docs for what this implies https://pbs.proxmox.com/docs/user-management.html#access-roles
 
Chris said:
Well, that depends on what permissions you would like that user to have ;)
As is, you allow to perform remote config administration, creation and restore of owned backups on all datastores but only administration of the datastore NFS_Backup_PNFS_Backup_P. Please check the docs for what this implies https://pbs.proxmox.com/docs/user-management.html#access-roles
Click to expand...
Good morning,
Yes is what I want, because NFS_backup_p is a remote nfs storage which I use to cross with my nfs to relocate some backups.
So how can we proceed with my permission issue? Yesterday I started a datastore verify for both my nfs
 
g.migliaccio said:
Good morning,
Yes is what I want, because NFS_backup_p is a remote nfs storage which I use to cross with my nfs to relocate some backups.
So how can we proceed with my permission issue? Yesterday I started a datastore verify for both my nfs
Click to expand...
What do you mean? Does setting the correct user privileges not solve you permission issues? Did you check which user is used to create backups on the PVE side and if it has all the required privileges?
 
I use the remote_admin user just for sync operations betwee two pbs servers and their nfs datacenters, for backups I use the root@pam user.
this is my acl.cfg:
GNU nano 5.4 /etc/proxmox-backup/acl.cfg
acl:1:/:remote_admin@pbs:RemoteAdmin
acl:1:/datastore:remote_admin@pbs:DatastoreBackup
acl:1:/datastore/NFS_Backup_P:remote_admin@pbs:DatastoreAdmin
 
Last edited:
g.migliaccio said:
I use the remote_admin user just for sync operations betwee two pbs servers and their nfs datacenters, for backups I use the root@pam user.
this is my acl.cfg:
GNU nano 5.4 /etc/proxmox-backup/acl.cfg
acl:1:/:remote_admin@pbs:RemoteAdmin
acl:1:/datastore:remote_admin@pbs:DatastoreBackup
acl:1:/datastore/NFS_Backup_P:remote_admin@pbs:DatastoreAdmin
Click to expand...
Please post the output of cat /etc/pve/storage.cfg on the PVE host you are running the backup from.
 
Sure here is the output:

Code: 
Linux dl380gen10-2 5.15.30-2-pve #1 SMP PVE 5.15.30-3 (Fri, 22 Apr 2022 18:08:27 +0200) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Sep 12 12:46:54 CEST 2024 from 192.168.208.242 on pts/0
root@dl380gen10-2:~# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content vztmpl,iso,backup

lvmthin: local-lvm
        thinpool data
        vgname pve
        content rootdir,images

lvmthin: local-ssd
        thinpool local-ssd
        vgname local-ssd
        content images,rootdir
        nodes dl380gen10-2,dl380Gen10-1

nfs: BK_VM_242
        export /BK_VM_242
        path /mnt/pve/BK_VM_242
        server 192.168.208.4
        content backup
        prune-backups keep-all=1

nfs: BK_VM_240
        export /BK_VM_240
        path /mnt/pve/BK_VM_240
        server 192.168.208.4
        content backup
        prune-backups keep-all=1

nfs: BK_Exchange
        export /BK_VM_246_Exchange
        path /mnt/pve/BK_Exchange
        server 192.168.208.25
        content backup
        prune-backups keep-all=1

nfs: NASVM_TEMP
        export /TEMP
        path /mnt/pve/NASVM_TEMP
        server 192.168.208.7
        content backup
        prune-backups keep-all=1

pbs: ProxmoxBackupServer
        datastore NFS_Backups
        server 192.168.208.32
        content backup
        fingerprint 39:c5:41:83:8a:40:e8:71:c1:73:b9:57:93:3d:c7:f0:f1:3b:b6:93:b8:05:1f:d7:d1:ae:6d:48:6c:f2:43:74
        prune-backups keep-all=1
        username root@pam
 
And what are the permissions of the folders inside the datastores vm folder (again on the PBS)? Do you have write access on the mounted share as backup user? I guess so otherwise the backup would not even be able to start, but you seem to get errors when listing or pruning.
 
Chris said:
And what are the permissions of the folders inside the datastores vm folder (again on the PBS)? Do you have write access on the mounted share as backup user? I guess so otherwise the backup would not even be able to start, but you seem to get errors when listing or pruning.
Click to expand...

Absolutely correct I got write access to the vm's folders in PBS datastore but I'll check it again.
Code: 
root@pbs:~# ls -la /var/nfs_backups/vm
total 213
drwxrwxrwx 25 backup backup 25 Sep  7 08:49 .
drwxrwxrwx  6 backup backup  9 Sep  5 11:55 ..
drwxrwxrwx 22 backup backup 23 Sep 11 17:30 100
drwxrwxrwx 22 backup backup 23 Sep 11 17:30 101
drwxrwxrwx 22 backup backup 23 Sep 11 17:31 102
drwxrwxrwx 22 backup backup 23 Sep 11 17:34 103
drwxrwxrwx 13 backup backup 14 Sep 11 17:37 104
drwxrwxrwx 22 backup backup 23 Sep 11 17:43 105
drwxrwxrwx 22 backup backup 23 Sep 11 17:53 106
drwxrwxrwx 22 backup backup 23 Sep 11 17:56 107
drwxrwxrwx 22 backup backup 23 Sep 11 18:16 108
drwxrwxrwx 16 backup backup 17 Sep 11 18:30 109
drwxrwxrwx 15 backup backup 16 Sep  4 22:42 110
drwxrwxrwx 15 backup backup 16 Sep  4 22:42 111
drwxrwxrwx 22 backup backup 23 Sep 11 18:34 113
drwxrwxrwx 21 backup backup 22 Sep 11 18:40 114
drwxrwxrwx 19 backup backup 20 Sep 11 18:43 115
drwxrwxrwx 12 backup backup 13 Sep 11 18:46 116
drwxrwxrwx  8 backup backup  9 Sep 11 21:00 122
drwxrwxrwx  8 backup backup  9 Sep 11 21:04 124
drwxrwxrwx  3 backup backup  4 Sep  7 06:52 150
drwxrwxrwx  3 backup backup  4 Sep  7 07:08 151
drwxrwxrwx  5 backup backup  6 Sep  7 18:15 152
drwxrwxrwx  4 backup backup  5 Sep  7 18:19 153
drwxrwxrwx  4 backup backup  5 Sep  7 18:33 154
root@pbs:~# ls -la /var/nfs_backup_p/vm
total 187
drwxrwxrwx 22 backup backup 22 Jul 31 05:35 .
drwxrwx---  6 backup backup  9 Sep  6 17:04 ..
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 100
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 101
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 102
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 103
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 104
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 105
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 106
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 107
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 108
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 109
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 113
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 114
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 115
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 116
drwxrwxrwx 10 backup backup 11 Apr 19 10:51 124
drwxrwxrwx  3 backup backup  4 Jul 18 05:37 150
drwxrwxrwx  3 backup backup  4 Jul 18 05:50 151
drwxrwxrwx  4 backup backup  5 Aug  4 06:08 152
drwxrwxrwx  3 backup backup  4 Jul 24 05:38 153
drwxrwxrwx  3 backup backup  4 Jul 24 05:42 154
 
Last edited:
Check also the subfolders, especially with respect to VM 100, as that is the one for which the prune fails. Also, as what user are you accessing the WebUI?
 
Good morning Chris,
First of all thanks again for your precious time.
So this is the output for the /vm/100:

Code: 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Sep 13 09:17:02 CEST 2024 on pts/0
You have new mail.
root@pbs:~# ls -la /var/nfs_backup_pointel/vm/100
total 106
drwxrwxrwx 11 backup backup 12 Aug 30 05:00 .
drwxrwxrwx 22 backup backup 22 Jul 31 05:35 ..
drwxrwxrwx  2 backup backup  6 Aug  2 05:01 2024-07-31T21:00:05Z
drwxrwxrwx  2 backup backup  6 Aug 18 05:04 2024-08-16T21:00:04Z
drwxrwxrwx  2 backup backup  6 Aug 19 05:01 2024-08-17T21:00:00Z
drwxrwxrwx  2 backup backup  6 Aug 20 05:01 2024-08-18T21:00:04Z
drwxrwxrwx  2 backup backup  6 Aug 21 05:01 2024-08-19T21:00:00Z
drwxrwxrwx  2 backup backup  6 Aug 22 05:01 2024-08-20T21:00:03Z
drwxrwxrwx  2 backup backup  6 Aug 23 05:01 2024-08-21T21:00:58Z
drwxrwxrwx  2 backup backup  6 Aug 23 05:01 2024-08-22T21:00:03Z
d---rwxrwx  2 backup backup  2 Aug 30 05:00 2024-08-26T21:00:02Z
-rwxrwxrwx  1 backup backup  9 Oct 29  2022 owner

For the WebUi access I'm using root@pam
 
Chris this folder was empty, so I checked all the folders with same date and time as this one, every folder was empty, so i deleted all of them and this datastore (nfs_backup_p) is now ok!
I got the same issue on the other datastore but unfortunately no empty folders, can you please check this output?

Code: 
root@pbs:~# ls -la /var/nfs_backups/vm/100/2024-08-21T20:30:01Z
total 683
drwxrwxrwx  2 backup backup      6 Sep 11 15:05 .
drwxrwxrwx 22 backup backup     23 Sep 13 09:14 ..
-rwxrwxrwx  1 backup backup   2278 Aug 21 22:37 client.log.blob
-rwxrwxrwx  1 backup backup 659456 Aug 21 22:37 drive-virtio0.img.fidx
-rw-r--r--  1 backup backup    545 Sep 11 15:05 index.json.blob
-rwxrwxrwx  1 backup backup    310 Aug 21 22:29 qemu-server.conf.blob

I'll try to change the permissions on all *.blob files
 
Last edited:
Mybe i found the problem:

Code: 
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/101/2024-08-29T20:30:03Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/115/2024-08-29T20:30:07Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/106/2024-08-29T20:30:07Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/108/2024-08-29T20:30:03Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/102/2024-08-29T20:30:06Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/111/2024-08-29T20:30:04Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/105/2024-08-29T20:30:03Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/107/2024-08-29T20:30:07Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/114/2024-08-29T20:30:12Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/113/2024-08-29T20:30:12Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/100/2024-08-29T20:30:02Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:59 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/110/2024-08-29T20:30:04Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:59 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/103/2024-08-29T20:30:06Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:59 pbs proxmox-backup-proxy[747]: GET /api2/json/admin/datastore/NFS_Backups/snapshots?: 400 Bad Request: [client [::ffff:192.168.208.242]:46366] EACCES: Permission denied

I don't have this folder "2024-08-29T20:30" in no one of the vm's folders, there is a way to clear this cache?
 
Last edited:
g.migliaccio said:
Mybe i found the problem:

Code: 
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/101/2024-08-29T20:30:03Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/115/2024-08-29T20:30:07Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/106/2024-08-29T20:30:07Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/108/2024-08-29T20:30:03Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/102/2024-08-29T20:30:06Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/111/2024-08-29T20:30:04Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/105/2024-08-29T20:30:03Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/107/2024-08-29T20:30:07Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/114/2024-08-29T20:30:12Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/113/2024-08-29T20:30:12Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:58 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/100/2024-08-29T20:30:02Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:59 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/110/2024-08-29T20:30:04Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:59 pbs proxmox-backup-proxy[747]: error during snapshot file listing: 'unable to load blob '"/var/nfs_backups/vm/103/2024-08-29T20:30:06Z/index.json.blob"' - No such file or directory (os error 2)'
Sep 13 00:57:59 pbs proxmox-backup-proxy[747]: GET /api2/json/admin/datastore/NFS_Backups/snapshots?: 400 Bad Request: [client [::ffff:192.168.208.242]:46366] EACCES: Permission denied

I don't have this folder "2024-08-29T20:30" in no one of the vm's folders, there is a way to clear this cache?
Click to expand...
No caching, but maybe you should restart the proxmox-backup and proxmox-backup-proxy once more. Once again, could it be that the datastore got mounted after the service started? Because there is a file handle kept open for the datastore, so you might actually access the storage below if it got mounted over.
 
Chris said:
No caching, but maybe you should restart the proxmox-backup and proxmox-backup-proxy once more. Once again, could it be that the datastore got mounted after the service started? Because there is a file handle kept open for the datastore, so you might actually access the storage below if it got mounted over.
Click to expand...
I can restart all the backup server without problems, and no the nfs mount is just there from before the restart.
If there is a way to check this file I can check for you
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom