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

DOCS-412: Node and Drive Recovery Procedures

Browse Source 
Klaus suggestions

Adding Eco's suggestions

Co-authored-by: Eco <41090896+eco-minio@users.noreply.github.com>

CR updates

Additional review comments

final work
This commit is contained in:
ravindk89
2022-01-11 18:25:02 -05:00
committed by Ravind Kumar
parent a6fb44ac60
commit ef4541a085
8 changed files with 285 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
source/includes/common-installation.rst
View File

@ -197,10 +197,18 @@ Console.
.. start-local-jbod-desc
MinIO strongly recommends local :abbr:`JBOD (Just a Bunch of Disks)` arrays with
XFS-formatted disks for best performance. RAID or similar technologies do not
provide additional resilience or availability benefits when used with
distributed MinIO deployments, and typically reduce system performance.
MinIO strongly recommends direct-attached :abbr:`JBOD (Just a Bunch of Disks)`
arrays with XFS-formatted disks for best performance.
- Direct-Attached Storage (DAS) has significant performance and consistency
advantages over networked storage (NAS, SAN, NFS).
- Deployments using non-XFS filesystems (ext4, btrfs, zfs) tend to have
lower performance while exhibiting unexpected or undesired behavior.
- RAID or similar technologies do not provide additional resilience or
availability benefits when used with distributed MinIO deployments, and
typically reduce system performance.
Ensure all nodes in the |deployment| use the same type (NVMe, SSD, or HDD) of
drive with identical capacity (e.g. ``N`` TB) . MinIO does not distinguish drive