minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-31 18:04:52 +03:00
Code Activity

Clarify existing data behavior

Browse Source
This commit is contained in:
Ravind Kumar
2022-06-02 16:16:24 -04:00
committed by Ravind Kumar
parent bedb656de7
commit 7817d8c48a
1 changed files with 7 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
source/installation/deploy-minio-standalone.rst
View File

@ -22,31 +22,17 @@ Starting with :minio-release:`RELEASE.2022-06-02T02-11-04Z`, MinIO implements a
This feature allows access to :ref:`erasure coding dependent features <minio-erasure-coding>` without the requirement of multiple drives. 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. The specified data volume or folder *must* be empty *or* only contain files generated by a previous |SNSD| deployment.
Starting MinIO against a folder with existing filesystem data (e.g. not MinIO-created or managed) retains the legacy filesystem behavior. Specifically: Use an earlier version of MinIO to retain the legacy filesystem-access behavior.
- Top-level folders at the starting path become MinIO buckets. .. admonition:: MinIO Avoids Root Disks
- Files in folders within the starting path become objects within the MinIO buckets. :class: important
- Files in the top-level starting path do not display in MinIO.
Consider a starting path with the following structure: MinIO by default avoids using the root OS disk as part of startup and returns an error if the specifid path is part of the root disk.
.. code-block:: You can specify the environment variable ``MINIO_CI_CD=1`` to allow using root disks.
/data
file.txt
/foo
file2.txt
/bar
file3.txt
When you deploy the server with a starting path of ``/data``, MinIO displays the data as follows: This variable is intended primarily for CI/CD environments or local testing/evaluation.
MinIO does not support usage outside of those specific use cases.
- Two buckets, ``foo`` and ``bar``
- ``file2.txt`` displays in the ``foo`` bucket
- ``file3.txt`` displays in the ``bar`` bucket
- ``file.txt`` does not display in MinIO anywhere, but remains available through the file system
A MinIO deployment in filesystem mode does *not* support any :ref:`erasure coding features <minio-erasure-coding>` such as versioning or object locking.
.. _deploy-minio-standalone: .. _deploy-minio-standalone: