diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2018-05-10 11:18:49 -0400 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2018-05-10 11:18:49 -0400 |
| commit | 28700a36232ba61fb6ac59466821546cb25aec69 (patch) | |
| tree | 44edd77f7ff77058cb725aef6c25810527a212f7 | |
| parent | 65972a6fa914b16cc15ffcffcb8bea8c64e78f49 (diff) | |
dm thin: update Documentation to clarify when "read_only" is valid
Due to user confusion, clarify that it doesn't make sense to try to
create a thin-pool with "read_only" mode enabled.
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
| -rw-r--r-- | Documentation/device-mapper/thin-provisioning.txt | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/device-mapper/thin-provisioning.txt b/Documentation/device-mapper/thin-provisioning.txt index 4bcd4b7f79f9..3d01948ea061 100644 --- a/Documentation/device-mapper/thin-provisioning.txt +++ b/Documentation/device-mapper/thin-provisioning.txt @@ -264,7 +264,10 @@ i) Constructor data device, but just remove the mapping. read_only: Don't allow any changes to be made to the pool - metadata. + metadata. This mode is only available after the + thin-pool has been created and first used in full + read/write mode. It cannot be specified on initial + thin-pool creation. error_if_no_space: Error IOs, instead of queueing, if no space. |