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
~~~~~~~~~~~~~~~~~~~~~~~~~
shared::
-Mark storage as shared.
+Indicate that this is a single storage with the same contents on all nodes (or
+all listed in the 'nodes' option). It will not make the contents of a local
+storage automatically accessible to other nodes, it just marks an already shared
+storage as such!
disable::
associated volumes which are owned by that VM or Container.
-Using the Command Line Interface
+Using the Command-line Interface
--------------------------------
It is recommended to familiarize yourself with the concept behind storage
allocation and removal of volumes is done by the VM and Container
management tools.
-Nevertheless, there is a command line tool called `pvesm` (``{pve}
+Nevertheless, there is a command-line tool called `pvesm` (``{pve}
Storage Manager''), which is able to perform common storage management
tasks.
List iso images
- pvesm list <STORAGE_ID> --iso
+ pvesm list <STORAGE_ID> --content iso
List container templates
- pvesm list <STORAGE_ID> --vztmpl
+ pvesm list <STORAGE_ID> --content vztmpl
Show file system path for a volume
* link:/wiki/Storage:_ZFS[Storage: ZFS]
-* link:/wiki/Storage:_ZFS_over_iSCSI[Storage: ZFS over iSCSI]
+* link:/wiki/Storage:_ZFS_over_ISCSI[Storage: ZFS over ISCSI]
endif::wiki[]