- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for denied (0.2 sec)
-
docs/distributed/DESIGN.md
- Choice of erasure set size is automatic based on the number of drives available, let's say for example if there are 32 servers and 32 drives which is a total of 1024 drives. In this scenario 16 becomes the erasure set size. This is decided based on the greatest common divisor (GCD) of acceptable erasure set sizes ranging from *4 to 16*.
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Tue Aug 15 23:04:20 GMT 2023 - 8K bytes - Viewed (0) -
docs/bucket/lifecycle/DESIGN.md
Lifecycle transition rules can be applied to buckets (both versioned and un-versioned) by specifying the tier name defined above as the transition storage class for the lifecycle rule. ## Implementation
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4.3K bytes - Viewed (0) -
docs/bucket/versioning/DESIGN.md
`xl.meta` is a new self describing backend format used by MinIO to support AWS S3 compatible versioning. This file is the source of truth for each `version` at rest. `xl.meta` is a msgpack file serialized from a well defined data structure. To understand `xl.meta` here are the few things to start with `xl.meta` carries first 8 bytes an XL header which describes the current format and the format version,
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sun Jul 17 15:43:14 GMT 2022 - 5.8K bytes - Viewed (1)