Am 02.05.23 um 15:17 schrieb Aaron Lauterer: > Scan the VM config and store the volid and full path for each storage. > Do the same when we scan each storage. Then we can have these > scenarios: > * multiple storage configurations might point to the same storage > The result is, that when scanning the storages, we find the disk image > multiple times. > -> we ignore them >
Having the same storage with overlapping content types is a configuration error (except if you use different 'content-dirs' I guess). We can't make guarantees for locking, which e.g. leads to races for allocation, it can lead to left-over references, etc.. Rather than trying to handle this here, I'd prefer a warning about the misconfiguration somewhere (maybe during storage.cfg parsing?) and/or error out when attempting to create such a configuration. Adding something in the docs also makes sense if there isn't yet. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
