> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/nas/nas-local-volumes.md).

# Local Volumes

How to create and configure local NAS volumes in VergeOS, including encryption, storage tiering, snapshot profiles, and size management on the vSAN.

Local volumes are file systems stored within VergeOS, consuming storage in the VergeOS vSAN. Each local volume can have different sharing, syncing, tiering, and permission settings.

{% hint style="success" %}
**A NAS service must be in place before creating volumes. See the** [**NAS Service**](/run-the-platform/nas/nas-service.md) **page for instructions.**
{% endhint %}

## Create a Local Volume

1. Navigate to **NAS** > **Volumes**.
2. Select **New** from the left menu.
3. Select the appropriate **NAS Service** from the dropdown list.
4. Enter a **Name** for the volume (required). Note: spaces are not permitted.
5. Enter a **Description** for the volume (optional).
6. In the **Filesystem Type** dropdown list, select ***Local Volume (EXT4)***.
7. The **Encrypt Volume** option can be selected to encrypt the entire volume (AES-XTS).

{% hint style="info" %}
**Encryption Considerations:**

* Encryption selection is only available during creation; a volume cannot be changed from encrypted to unencrypted or vice-versa after creation.
* Minor to moderate performance implications are involved with enabling volume encryption.
  {% endhint %}

8. When encryption is selected, **Encryption Key** is also required.

{% hint style="warning" %}
**The encryption key is needed for the lifetime of the volume. This encryption key must be entered each time the volume is brought online (e.g. after disabling/enabling a volume or after its NAS service is rebooted, etc.) Without the encryption key, it will not be possible to bring the volume back online!**
{% endhint %}

9. Specify a **Max Size** for the volume, by entering an integer and selecting the unit (B/KB/MB/GB/TB). (When max size is reached, the volume will show out of space and will continue to be readable, but will not allow further writes.)
10. The **Discard** option is enabled by default. When discard enabled: as data is deleted from the volume, that space is reclaimed back to the vSAN.
11. The volume can optionally be set to **Read Only**.
12. The **Automatically Mount Snapshots** option can be selected to make snapshots readily available for browsing/file restores.
13. Specify **Owner** for the volume directory (optional).
14. Specify a **Group** for volume directory (optional).
15. Select a **Snapshot Profile** for the volume (optional). See [**Snapshot Profiles**](/automate-protect-and-extend/backup-and-dr/snapshot-profiles.md) for information regarding snapshot profiles.
16. Select **Preferred Tier** for storing this volume. Preferred tier is the tier first attempted. See [**Preferred Tiers**](/run-the-platform/storage/preferred-tiers.md) for more information.
17. Click **Submit** to save the settings and create the local volume.
18. The dashboard for the new local volume is displayed. It may take a few minutes for the new volume to come online. If the volume status does not become online, refer to the logs section (bottom of dashboard) to view error messages for troubleshooting.
19. Files in the online volume can be viewed using the **Browse** option from the left menu.
20. To expose the local volume, create CIFS and/or NFS [**shares**](/run-the-platform/nas/nas-shares.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verge.io/run-the-platform/nas/nas-local-volumes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.