mirror of
https://github.com/minio/minio.git
synced 2025-11-07 12:52:58 -05:00
docs: fix all Chinese doc links for the new docs site (#6097)
Additionally fix typos, default to US locale words
This commit is contained in:
@@ -18,7 +18,7 @@ Erasure code protects data from multiple drives failure, unlike RAID or replicat
|
||||
|
||||
## What is Bit Rot protection?
|
||||
|
||||
Bit Rot, also known as data rot or silent data corruption is a data loss issue faced by disk drives today. Data on the drive may silently get corrupted without signalling an error has occurred, making bit rot more dangerous than a permanent hard drive failure.
|
||||
Bit Rot, also known as data rot or silent data corruption is a data loss issue faced by disk drives today. Data on the drive may silently get corrupted without signaling an error has occurred, making bit rot more dangerous than a permanent hard drive failure.
|
||||
|
||||
Minio's erasure coded backend uses high speed [HighwayHash](https://blog.minio.io/highwayhash-fast-hashing-at-over-10-gb-s-per-core-in-golang-fee938b5218a) checksums to protect against Bit Rot.
|
||||
|
||||
|
||||
@@ -11,8 +11,8 @@ saving the object in specific number of data and parity disks.
|
||||
|
||||
## Storage usage
|
||||
|
||||
The selection of varying data and parity drives has a direct impact on the drive space usage. With storage class, you can optimise for high
|
||||
redundancy or better drive space utilisation.
|
||||
The selection of varying data and parity drives has a direct impact on the drive space usage. With storage class, you can optimize for high
|
||||
redundancy or better drive space utilization.
|
||||
|
||||
To get an idea of how various combinations of data and parity drives affect the storage usage, let’s take an example of a 100 MiB file stored
|
||||
on 16 drive Minio deployment. If you use eight data and eight parity drives, the file space usage will be approximately twice, i.e. 100 MiB
|
||||
|
||||
Reference in New Issue
Block a user