content type like virtual disk images, containers, templates, ISO images
or backup files.
content type like virtual disk images, containers, templates, ISO images
or backup files.
and then define a directory storage for that mount point. This way you
can use any file system supported by Linux.
This backend assumes that the underlying directory is POSIX
compatible, but nothing else. This implies that you cannot create
and then define a directory storage for that mount point. This way you
can use any file system supported by Linux.
This backend assumes that the underlying directory is POSIX
compatible, but nothing else. This implies that you cannot create
cache mode `none` with such storages. Simply use cache mode
`writeback` instead.
We use a predefined directory layout to store different content types
cache mode `none` with such storages. Simply use cache mode
`writeback` instead.
We use a predefined directory layout to store different content types
storage backends.
.Directory layout
[width="100%",cols="d,m",options="header"]
|===========================================================
|Content type |Subdir
storage backends.
.Directory layout
[width="100%",cols="d,m",options="header"]
|===========================================================
|Content type |Subdir
-|VM images |images/<VMID>/
-|ISO images |template/iso/
-|Container templates |template/cache
-|Backup files |dump/
+|VM images |`images/<VMID>/`
+|ISO images |`template/iso/`
+|Container templates |`template/cache/`
+|Backup files |`dump/`
+|Snippets |`snippets/`
additional property called `path` to specify the directory. This
needs to be an absolute file system path.
additional property called `path` to specify the directory. This
needs to be an absolute file system path.
Above configuration defines a storage pool called `backup`. That pool
can be used to store up to 7 backups (`maxfiles 7`) per VM. The real
Above configuration defines a storage pool called `backup`. That pool
can be used to store up to 7 backups (`maxfiles 7`) per VM. The real
-This scan be an arbitrary name (`ascii`) without white spaces. The
-backend uses `disk[N]` as default, where `[N]` is replaced by an
+This can be an arbitrary name (`ascii`) without white space. The
+backend uses `disk-[N]` as default, where `[N]` is replaced by an
-important that those files are read-only, and never gets modified. The
-backend changes access mode to `0444`, and sets the immutable flag
+important that those files are read-only, and never get modified. The
+backend changes the access mode to `0444`, and sets the immutable flag
of the box. To workaround that problem, this backend is able to use
`qcow2` internal snapshot capabilities.
of the box. To workaround that problem, this backend is able to use
`qcow2` internal snapshot capabilities.
.Storage features for backend `dir`
[width="100%",cols="m,m,3*d",options="header"]
|==============================================================================
.Storage features for backend `dir`
[width="100%",cols="m,m,3*d",options="header"]
|==============================================================================
-|Content types |Image formats |Shared |Snapshots |Clones
-|images rootdir vztempl iso backup |raw qcow2 vmdk subvol |no |qcow2 |qcow2
+|Content types |Image formats |Shared |Snapshots |Clones
+|images rootdir vztmpl iso backup snippets |raw qcow2 vmdk subvol |no |qcow2 |qcow2
# pvesm alloc local 100 vm-100-disk10.raw 4G
Formatting '/var/lib/vz/images/100/vm-100-disk10.raw', fmt=raw size=4294967296
# pvesm alloc local 100 vm-100-disk10.raw 4G
Formatting '/var/lib/vz/images/100/vm-100-disk10.raw', fmt=raw size=4294967296