From a6b885b333507d1d4a43f24568cc0bc834462fbe Mon Sep 17 00:00:00 2001 From: hamistao Date: Tue, 9 Apr 2024 16:13:58 -0300 Subject: [PATCH] doc: Update block volume usage Signed-off-by: hamistao --- doc/explanation/storage.md | 4 ++-- doc/howto/storage_volumes.md | 1 + 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/explanation/storage.md b/doc/explanation/storage.md index 51b6eca493a3..1f06cad5a740 100644 --- a/doc/explanation/storage.md +++ b/doc/explanation/storage.md @@ -132,7 +132,7 @@ Storage volumes can be of the following types: `custom` : You can add one or more custom storage volumes to hold data that you want to store separately from your instances. - Custom storage volumes can be shared between instances, and they are retained until you delete them. + Custom storage volumes of content type `filesystem` or `iso` can be shared between instances, and they are retained until you delete them. You can also use custom storage volumes to hold your backups or images. @@ -154,7 +154,7 @@ Each storage volume uses one of the following content types: You can create a custom storage volume of type `block` by using the `--type=block` flag. Custom storage volumes of content type `block` can only be attached to virtual machines. - They should not be shared between instances, because simultaneous access can lead to data corruption. + By default they can only be attached to one instance at a time, because simultaneous access can lead to data corruption. `iso` : This content type is used for custom ISO volumes. diff --git a/doc/howto/storage_volumes.md b/doc/howto/storage_volumes.md index 82ab34d40743..12e983e2efa9 100644 --- a/doc/howto/storage_volumes.md +++ b/doc/howto/storage_volumes.md @@ -53,6 +53,7 @@ The following restrictions apply: - To avoid data corruption, storage volumes of {ref}`content type ` `block` should never be attached to more than one virtual machine at a time. - Storage volumes of {ref}`content type ` `iso` are always read-only, and can therefore be attached to more than one virtual machine at a time without corrupting data. - File system storage volumes can't be attached to virtual machines while they're running. +- Custom block storage volumes that don't have `security.shared` enabled cannot be attached to more than one instance at the same time. For custom storage volumes with the content type `filesystem`, use the following command, where `` is the path for accessing the storage volume inside the instance (for example, `/data`):