Proxmox-NFS Storage Directory Config

Software & Web Applications
1

Can someone help me understand if I am doing something wrong or misinterpreting this? https://pve.proxmox.com/pve-docs/pve-admin-guide.html#\_configuration_2

It says “comma-separated list of identifiers in the following format:

vtype=path

The following does not work:

nfs: truenas
        export /mnt/tank/ISOs
        path /mnt/pve/truenas
        server 192.168.1.3
        content iso
        prune-backups keep-all=1
        content-dirs iso=/Linux, iso=/Windows

It only shows the last directory in the comma separated list. I have tried every combination I can think of for comma separated lists and they either show nothing, or they only show the last one in the list.

2

Hmmm…. I always do this in the GUI. Each export is independent:

nfs: nas-prime-isos
	export /volume2/ISOs
	path /mnt/pve/nas-prime-isos
	server 172.16.1.1
	content vztmpl,iso
	prune-backups keep-all=1

nfs: nas-prime-nfs-vol1
	export /volume1/proxmox-nfs
	path /mnt/pve/nas-prime-nfs-vol1
	server 172.16.1.1
	content rootdir,images
	prune-backups keep-all=1
1 Like
3

It may be the space after the commas that’s causing in not to work. Typically comma-separated configs treat everything that’s not a comma as part of the argument, so it may be parsing that space as the beginning of the next key/value pair.

1 Like
4

Like I said, I tried every combination of comma separated list I could think of or find. With quotes, with spaces before the comma, no spaces. It would be nice if they gave an example in the documentation but, that is why I am baffled and curious if I am misinterpreting what they are saying.

5

That’s how I have it now, no choice, but the documentation states you should be able to use a comma separated list for them.

6

You can use comma separated ONLY for different VTYPES, that is, one for ISOs, one for backup files, one for VMs, etc. You are trying to set two different paths for ISOs, I don’t think that is possible

Screenshot 2025-09-03 052949
Screenshot 2025-09-03 0529491065×648 106 KB

1 Like
7

I think that is a horrible implementation if that is true. Why would they not allow multiple paths? What would stop the underlying code from seeing subfolders? At least allow the content type to be a directory.

Thank you for bringing that to my attention. They should clarify that better if that is the case.

1 Like
8

well the answer is, how would Proxmox be able to tell what is a windows ISO vs a Linux ISO. To the software, an ISO is an ISO. Nothing is stopping you (I think) from manually creating sub directories in the ISO directory, once Proxmox creates it.

1 Like
9

That’s not how it works. The content type is what it looks for, so if you put a subdirectory within the one it creates it will not see anything because it is looking for the content type of ISO. It cannot traverse subdirectories as it takes absolute paths.

That is why using the above you can point it to a “custom” directory or subfolder but not multiple.