minio/docs

mirror of https://github.com/minio/docs.git synced 2025-04-22 19:02:57 +03:00

DOCS-IA: Platformize SSE Docs. Hashicorp Pass (#518 )

* Platformization of Data Encryption Docs: Hashicorp Pass

* Platformization of Data Encryption Docs: Hashicorp Pass

* Big pass, CR changes + K8s

2022-08-15 12:53:08 -04:00

3.2 KiB

Raw Blame History

Deploy MinIO: Single-Node Single-Drive

minio

Table of Contents

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 Standalone Mode or 'filesystem' mode.

Starting with 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 erasure coding dependent features <minio-erasure-coding> without the requirement of multiple drives.

MinIO only starts in mode if the storage volume or path is empty or only contain files generated by a previous deployment. See the documentation on SNSD behavior with pre-existing data <minio-snsd-pre-existing-data> for more information.

container

For extended development or production environments in orchestrated environments, use the MinIO Kubernetes Operator to deploy a Tenant on multiple worker nodes.

linux

For extended development or production environments, deploy MinIO in a Multi-Node Multi-Drive (Distributed) <minio-mnmd> topology

Pre-Existing Data

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:

Storage Volume State	Behavior
Empty with no files, folders, or MinIO backend data	MinIO starts in mode and creates the zero-parity backend
Existing zero-parity objects and MinIO backend data	MinIO resumes in 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 Single-Node Single-Drive MinIO

The following procedure deploys MinIO consisting of a single MinIO server and a single drive or storage volume.

Network File System Volumes Break Consistency Guarantees

MinIO's strict read-after-write and list-after-write consistency model requires local disk filesystems (xfs, ext4, etc.).

MinIO cannot provide consistency guarantees if the underlying storage volumes are NFS or a similar network-attached storage volume.

For deployments that require using network-attached storage, use NFSv4 for best results.