[pve-devel] [PATCH v5 docs 10/10] storage: add hint to avoid storage aliasing

Aaron Lauterer a.lauterer at proxmox.com
Mon Jun 19 11:29:37 CEST 2023

Reviewed-by: Fiona Ebner <f.ebner at proxmox.com>
Signed-off-by: Aaron Lauterer <a.lauterer at proxmox.com>
changes since v4: none

 pvesm.adoc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/pvesm.adoc b/pvesm.adoc
index d250e0b..49eb972 100644
--- a/pvesm.adoc
+++ b/pvesm.adoc
@@ -177,6 +177,12 @@ zfspool: local-zfs
 	content images,rootdir
+CAUTION: It is problematic to have multiple storage configurations pointing to
+the exact same underlying storage. Such an _aliased_ storage configuration can
+lead to two different volume IDs ('volid') pointing to the exact same disk
+image. {pve} expects that the images' volume IDs point to, are unique. Choosing
+different content types for _aliased_ storage configurations can be fine, but
+is not recommended.
 Common Storage Properties

More information about the pve-devel mailing list