minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2026-01-04 02:44:36 +03:00
Code Activity

DOCS-495: Clean up SNSD Pre-Existing Data behavior

Browse Source
This commit is contained in:
Ravind Kumar
2022-06-13 18:17:28 -04:00
committed by Ravind Kumar
parent a2165bfe69
commit df33ddee6a
2 changed files with 31 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
source/concepts/erasure-coding.rst
View File

@@ -35,9 +35,7 @@ defaults to 4 parity blocks per object with tolerance for the loss of 4 drives
per erasure set. For more complete information on selecting erasure code parity,
see :ref:`minio-ec-parity`.
Erasure coding requires a minimum of 4 drives is only available with
:ref:`distributed <minio-installation-comparison>` MinIO deployments. Erasure
coding is a core requirement for the following MinIO features:
Erasure coding is a core requirement for the following MinIO features:
- :ref:`Object Versioning <minio-bucket-versioning>`
- :ref:`Server-Side Replication <minio-bucket-replication>`
@@ -53,7 +51,8 @@ Zero-Parity Deployments
Starting with :minio-release:`RELEASE.2022-06-02T02-11-04Z`, MinIO supports a Single-Node Single-Drive (SNSD) topology with a zero-parity erasure coding backend.
Zero-parity deployments necessarily depend on the underlying storage for resiliency and availability. Erasure Coding protections and behavior do not apply to |SNSD| deployments.
Erasure Coding protections do not apply to the zero-parity backend of |SNSD| deployments.
Zero-parity deployments depend on the underlying storage for resiliency and availability.
.. _minio-ec-erasure-set:

40
source/installation/deploy-minio-single-node-single-drive.rst
View File

@@ -11,26 +11,42 @@ Deploy MinIO as Single-Node Single-Drive
The procedures on this page cover deploying MinIO in a Single-Node Single-Drive (SNSD) configuration for early development and evaluation.
This mode was previously called :guilabel:`Standalone Mode` or 'filesystem' mode.
For extended development or production environments, deploy MinIO
in :guilabel:`Distributed Mode`. See :ref:`deploy-minio-distributed` for more
information.
Starting with :minio-release:`RELEASE.2022-06-02T02-11-04Z`, MinIO implements a zero-parity erasure coded backend for single-node single-drive deployments.
This feature allows access to :ref:`erasure coding dependent features <minio-erasure-coding>` without the requirement of multiple drives.
MinIO only starts in |SNSD| mode if the storage volume or path is empty *or* only contain files generated by a previous |SNSD| deployment.
See :ref:`minio-snsd-pre-existing-data <minio-snsd-pre-existing-data>` for more complete documentation on MinIO startup behavior in |SNSD| mode.
For extended development or production environments, deploy MinIO in :guilabel:`Distributed Mode`. See :ref:`deploy-minio-distributed` for more information.
.. _minio-snsd-pre-existing-data:
Pre-Existing Data
-----------------
Starting with :minio-release:`RELEASE.2022-06-02T02-11-04Z`, MinIO implements a zero-parity erasure coded backend for single-node single-drive deployments.
This feature allows access to :ref:`erasure coding dependent features <minio-erasure-coding>` without the requirement of multiple drives.
The specified data volume or folder *must* be empty *or* only contain files generated by a previous |SNSD| deployment.
MinIO startup behavior depends on the the contents of the specified storage volume or path.
The server checks for both MinIO-internal backend data and the structure of existing folders and files.
The following table lists the possible storage volume states and MinIO behavior:
Use an earlier version of MinIO to retain the legacy filesystem-access behavior.
.. list-table::
:header-rows: 1
:widths: 40 60
.. admonition:: MinIO Avoids Root Disks
:class: important
* - Storage Volume State
- Behavior
By default MinIO returns an error if the specified path is part of the root or OS drive.
* - Empty with **no** files, folders, or MinIO backend data
- MinIO starts in |SNSD| mode and creates the zero-parity backend
Specify the environment variable ``MINIO_CI_CD=1`` to direct MinIO to use the root disk in CI/CD environments or for local testing and evaluation.
MinIO does not support usage of this environment variable outside of these use cases.
* - Existing |SNSD| zero-parity objects and MinIO backend data
- MinIO resumes in |SNSD| mode
* - Existing filesystem folders, files, and MinIO backend data
- MinIO resumes in the legacy filesystem ("Standalone") mode with no erasure-coding features
* - Existing filesystem folders, files, but **no** MinIO backend data
- MinIO returns an error and does not start
.. _deploy-minio-standalone: