minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-28 19:42:10 +03:00
Code Activity

Mc updates for multiple releases (#642)

Browse Source 
Updates `mc` reference docs for several releases of the MinIO Client.

- Adds missing flags to `mc admin trace`
- Updates `disk` -> `drive` throughout the docs, but not in all cases.
- Adds `--airgap flag` to `mc support profile` and `mc support perf`
commands.
- Updates the flags for `mc ilm add` command
- Adds `mc license unregister` command.
    
Closes #571
Closes #614
Closes #627
Closes #633
This commit is contained in:
Daryl White
2022-11-18 12:49:03 -06:00
committed by GitHub
parent 2f8c5a94f6
commit 0cd491c328
36 changed files with 291 additions and 140 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
source/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst
View File

@ -94,7 +94,7 @@ Local JBOD Storage with Sequential Mounts
:class: note
MinIO's strict **read-after-write** and **list-after-write** consistency
model requires local disk filesystems.
model requires local drive filesystems.
MinIO cannot provide consistency guarantees if the underlying storage
volumes are NFS or a similar network-attached storage volume.
@ -252,7 +252,7 @@ The following examples assumes that:
minio1.example.com minio3.example.com
minio2.example.com minio4.example.com
- All hosts have four locally-attached disks with sequential mount-points:
- All hosts have four locally-attached drives with sequential mount-points:
.. code-block:: shell

2
source/operations/install-deploy-manage/deploy-minio-single-node-multi-drive.rst
View File

@ -39,7 +39,7 @@ Local JBOD Storage with Sequential Mounts
:class: note
MinIO's strict **read-after-write** and **list-after-write** consistency
model requires local disk filesystems.
model requires local drive filesystems.
MinIO cannot provide consistency guarantees if the underlying storage
volumes are NFS or a similar network-attached storage volume.

2
source/operations/install-deploy-manage/deploy-minio-single-node-single-drive.rst
View File

@ -77,7 +77,7 @@ The following procedure deploys MinIO consisting of a single MinIO server and a
:class: note
MinIO's strict **read-after-write** and **list-after-write** consistency
model requires local disk filesystems (``xfs``, ``ext4``, etc.).
model requires local drive filesystems (``xfs``, ``ext4``, etc.).
MinIO cannot provide consistency guarantees if the underlying storage
volumes are NFS or a similar network-attached storage volume.

8
source/operations/install-deploy-manage/expand-minio-deployment.rst
View File

@ -21,7 +21,7 @@ MinIO supports expanding an existing distributed deployment by adding a new
:ref:`Server Pool <minio-intro-server-pool>`. Each Pool expands the total
available storage capacity of the cluster while maintaining the overall
:ref:`availability <minio-erasure-coding>` of the cluster. Each Pool is its
own failure domain, where the loss of one or more disks or nodes in that pool
own failure domain, where the loss of one or more drives or nodes in that pool
does not effect the availability of other pools in the deployment.
The procedure on this page expands an existing
@ -104,7 +104,7 @@ Local JBOD Storage with Sequential Mounts
:class: note
MinIO's strict **read-after-write** and **list-after-write** consistency
model requires local disk filesystems (``xfs``, ``ext4``, etc.).
model requires local drive filesystems (``xfs``, ``ext4``, etc.).
MinIO cannot provide consistency guarantees if the underlying storage
volumes are NFS or a similar network-attached storage volume.
@ -158,7 +158,7 @@ MinIO calculates the probability of a write operation to each of the pools as:
- Pool B: 20% chance (:math:`2TiB / 10TiB`)
- Pool C: 50% chance (:math:`5TiB / 10TiB`)
In addition to the free space calculation, if a write option (with parity) would bring a disk
In addition to the free space calculation, if a write option (with parity) would bring a drive
usage above 99% or a known free inode count below 1000, MinIO does not write to the pool.
If desired, you can manually initiate a rebalance procedure with :mc:`mc admin rebalance`.
@ -321,7 +321,7 @@ The following examples assumes that:
minio7.example.com minio11.example.com
minio8.example.com minio12.example.com
- All hosts have eight locally-attached disks with sequential mount-points:
- All hosts have eight locally-attached drives with sequential mount-points:
.. code-block:: shell

2
source/operations/install-deploy-manage/expand-minio-tenant.rst
View File

@ -38,7 +38,7 @@ Locally Attached Drives
~~~~~~~~~~~~~~~~~~~~~~~
MinIO *strongly recommends* using locally attached drives on each node intended to support the new tenant pool to ensure optimal performance.
MinIO’s strict read-after-write and list-after-write consistency model requires local disk filesystems (xfs, ext4, etc.).
MinIO’s strict read-after-write and list-after-write consistency model requires local drive filesystems (xfs, ext4, etc.).
MinIO automatically generates :kube-docs:`Persistent Volume Claims (PVC) <concepts/storage/persistent-volumes/#persistentvolumeclaims>` as part of deploying a MinIO Tenant.
The Operator generates one PVC for each volume in the new pool.