6 :title: Storage: Directory
9 Storage pool type: `dir`
11 {pve} can use local directories or locally mounted shares for
12 storage. A directory is a file level storage, so you can store any
13 content type like virtual disk images, containers, templates, ISO images
16 NOTE: You can mount additional storages via standard linux `/etc/fstab`,
17 and then define a directory storage for that mount point. This way you
18 can use any file system supported by Linux.
20 This backend assumes that the underlying directory is POSIX
21 compatible, but nothing else. This implies that you cannot create
22 snapshots at the storage level. But there exists a workaround for VM
23 images using the `qcow2` file format, because that format supports
26 TIP: Some storage types do not support `O_DIRECT`, so you can't use
27 cache mode `none` with such storages. Simply use cache mode
30 We use a predefined directory layout to store different content types
31 into different sub-directories. This layout is used by all file level
35 [width="100%",cols="d,m",options="header"]
36 |===========================================================
38 |VM images |`images/<VMID>/`
39 |ISO images |`template/iso/`
40 |Container templates |`template/cache/`
41 |Backup files |`dump/`
42 |Snippets |`snippets/`
43 |===========================================================
49 This backend supports all common storage properties, and adds an
50 additional property called `path` to specify the directory. This
51 needs to be an absolute file system path.
53 .Configuration Example (`/etc/pve/storage.cfg`)
61 Above configuration defines a storage pool called `backup`. That pool
62 can be used to store up to 7 backups (`maxfiles 7`) per VM. The real
63 path for the backup files is `/mnt/backup/dump/...`.
66 File naming conventions
67 ~~~~~~~~~~~~~~~~~~~~~~~
69 This backend uses a well defined naming scheme for VM images:
71 vm-<VMID>-<NAME>.<FORMAT>
75 This specifies the owner VM.
79 This can be an arbitrary name (`ascii`) without white space. The
80 backend uses `disk-[N]` as default, where `[N]` is replaced by an
81 integer to make the name unique.
85 Specifies the image format (`raw|qcow2|vmdk`).
87 When you create a VM template, all VM images are renamed to indicate
88 that they are now read-only, and can be used as a base image for clones:
90 base-<VMID>-<NAME>.<FORMAT>
92 NOTE: Such base images are used to generate cloned images. So it is
93 important that those files are read-only, and never get modified. The
94 backend changes the access mode to `0444`, and sets the immutable flag
95 (`chattr +i`) if the storage supports that.
101 As mentioned above, most file systems do not support snapshots out
102 of the box. To workaround that problem, this backend is able to use
103 `qcow2` internal snapshot capabilities.
105 Same applies to clones. The backend uses the `qcow2` base image
106 feature to create clones.
108 .Storage features for backend `dir`
109 [width="100%",cols="m,m,3*d",options="header"]
110 |==============================================================================
111 |Content types |Image formats |Shared |Snapshots |Clones
112 |images rootdir vztmpl iso backup snippets |raw qcow2 vmdk subvol |no |qcow2 |qcow2
113 |==============================================================================
119 Please use the following command to allocate a 4GB image on storage `local`:
121 # pvesm alloc local 100 vm-100-disk10.raw 4G
122 Formatting '/var/lib/vz/images/100/vm-100-disk10.raw', fmt=raw size=4294967296
123 successfully created 'local:100/vm-100-disk10.raw'
125 NOTE: The image name must conform to above naming conventions.
127 The real file system path is shown with:
129 # pvesm path local:100/vm-100-disk10.raw
130 /var/lib/vz/images/100/vm-100-disk10.raw
132 And you can remove the image with:
134 # pvesm free local:100/vm-100-disk10.raw
142 * link:/wiki/Storage[Storage]