1
0
mirror of https://github.com/minio/docs.git synced 2025-07-30 07:03:26 +03:00

Further clarify SNSD + 0 parity mode access

This commit is contained in:
Ravind Kumar
2023-11-28 19:25:58 -05:00
parent 072b82c1e4
commit b3e259b6e6

View File

@ -15,6 +15,7 @@ The procedures on this page cover deploying MinIO in a Single-Node Single-Drive
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.
This mode **requires** accessing stored objects through the S3 API, and does **not** support direct access to objects through the filesystem/POSIX interface.
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 the documentation on :ref:`SNSD behavior with pre-existing data <minio-snsd-pre-existing-data>` for more information.
@ -99,4 +100,4 @@ The following procedure deploys MinIO consisting of a single MinIO server and a
.. cond:: windows
.. include:: /includes/windows/steps-deploy-minio-single-node-single-drive.rst
.. include:: /includes/windows/steps-deploy-minio-single-node-single-drive.rst