[pve-devel] [PATCH v3 docs 7/7] storage: add hint to avoid storage aliasing

Fiona Ebner f.ebner at proxmox.com
Fri Jun 2 13:51:48 CEST 2023

Am 01.06.23 um 15:53 schrieb Aaron Lauterer:
> Signed-off-by: Aaron Lauterer <a.lauterer at proxmox.com>
> ---
> I am happy for suggestions on how to improve the phrasing if it is not
> clear enough.
>  pvesm.adoc | 3 +++
>  1 file changed, 3 insertions(+)
> diff --git a/pvesm.adoc b/pvesm.adoc
> index 6ade1a4..7e91c50 100644
> --- a/pvesm.adoc
> +++ b/pvesm.adoc
> @@ -174,6 +174,9 @@ zfspool: local-zfs
>  	content images,rootdir
>  ----
> +CAUTION: It is not advisable to have multiple storage configurations pointing
> +to the exact same underlying storage. Such an _aliased_ storage configuration
> +can lead to unexpected behavior.

s/not advisable/problematic/ would sound a bit stronger IMHO

Maybe give some rationale and mention that volume IDs are not unique
anymore with such a configuration and that PVE expects that in certain
places, maybe giving a quick example. And we could also mention that in
case the content types is different, it can be fine, but still not

More information about the pve-devel mailing list