system creating "images" folder on NFS shares

T

triks

Member
Oct 17, 2022
46
5
13
Australia
just wondering if anyone has seen this on their system and if there is a fix to prevent this?

Proxmox=NFS client / Synology NAS=NFS server
NFS Storage 'sharename' is on node 'local'

PVE 7.2-11
DSM 7.1.1-42962

thanks in advance.
 
Hi,
yes, if you select content type images for the storage, then Proxmox VE will create a folder for it, because it will store the images there. You can prevent it with pvesm set sharename --mkdir 0 upon storage activation, but the folder will still be created when you create an image on the storage.

What are you intending to use the storage for?
 
So it's not really a storage used by Proxmox VE then. If you still want to add it (I guess to see the usage?), then I'd recommend using pvesm set sharename --mkdir 0 --content ''. So there is no content added from Proxmox VE by accident ;)
 
Trying to solve this issue now with Proxmox 9.0.10 is yielding the following, which I am quite confused about:

Code: 
root@Concordex:~# pvesm set Desysia --create-subdirs 0
NOTE: The 'mkdir' option set for 'Desysia' is deprecated and will be removed in Proxmox VE 9. Use 'create-base-path' or 'create-subdirs' instead.
root@Concordex:~# pvesm set Desysia --create-base-path 0
NOTE: The 'mkdir' option set for 'Desysia' is deprecated and will be removed in Proxmox VE 9. Use 'create-base-path' or 'create-subdirs' instead.

How might we go about doing this now?
 
Hi @D3K17, this should be correct. To get rid of the warning remove the legacy mkdir option pvesm set Desysia --delete mkdir.
 
You must log in or register to reply here.
Top Bottom