[pve-devel] [PATCH storage] fix #2085: Handle non-default mount point in path() by introducing new mountpoint property

[Thomas Lamprecht]

On 11/12/19 12:18 PM, Fabian Ebner wrote:
> 
> I don't see a clean way to do the automatic adding of the mount point property (doing it in path() is possible, but we need to assume that our caller doesn't hold the lock on storage.cfg). Maybe it's better to just do the warning in activate_storage and leave it to the user to configure the mount point properly? It feels a bit weird for the plugin code to modify the config; is there an instance where it does?

You could just to this once at bootup, or initial mount.