MinIO RELEASE.2020-08-04T23-10-51Zstable Released Aug 05, 2020
Impact Score: 5/10

MinIO: Minor Bugfix Release

Source available โ€” automated, not human-reviewed

Component: minio ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified โ€” check source notes
๐Ÿ“„ .MD
โšก Executive Summary (TL;DR)

MinIO RELEASE.2020-08-04T23-10-51Z. Source highlight: *allows the server to start under situations where the disk is faulty*, this is to ensure that other

Who Does This Impact? (Role-Based Analysis)

๐Ÿ’ป Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

๐Ÿ“Š Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

โš™๏ธ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

โœจ New Features & Capabilities (1)

  • add CopyObject optimization when source and destination are same (#10170) (08/03/20) (Harshavardhana)

๐Ÿ”ง Bug Fixes & Patches (6)

  • fix: proxies set keep-alive timeouts to be system dependent (#10199) (08/04/20) (Harshavardhana)
  • fix: reduce an extra system call for writes instead fail later (#10187) (08/04/20) (Harshavardhana)
  • fix: multi-tenant deployment guide to use ellipses format (#10192) (08/04/20) (Harshavardhana)
  • fix ILM should not remove a protected version (#10189) (08/04/20) (Anis Elleuch)
  • fix: allow FS mode situations when conflicting files exist (#10185) (08/03/20) (Harshavardhana)
  • fix: quorum calculation mistake with reduced parity (#10186) (08/03/20) (Harshavardhana)
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
## Highlights - *allows the server to start under situations where the disk is faulty*, this is to ensure that other good drive(s) locally on the same node are usable. Previously we kept the servers down simply to provide more attention for the administrator to fix these drives, but in containerized environments this is not true and pods crashing can have other issues - to improve the situation for containerized environments allow the server to be operable - instead the administrator should look at `mc admin info` to look for faulty drives to be fixed/replaced, see #10175 - CopyObject optimization to avoid creating a new copy of the entire object if the destination is the same object copied from the same source object with versionId specified. #10170 - Allow write quorum calculation under reduced parity uniform across all write operations #10186 ## Changelog - fix: proxies set keep-alive timeouts to be system dependent (#10199) (08/04/20) (Harshavardhana) - fix: reduce an extra system call for writes instead fail later (#10187) (08/04/20) (Harshavardhana) - fix: multi-tenant deployment guide to use ellipses format (#10192) (08/04/20) (Harshavardhana) - fix ILM should not remove a protected version (#10189) (08/04/20) (Anis Elleuch) - allow server to start even with corrupted/faulty disks (#10175) (08/03/20) (Harshavardhana) - add CopyObject optimization when source and destination are same (#10170) (08/03/20) (Harshavardhana) - fix: allow FS mode situations when conflicting files exist (#10185) (08/03/20) (Harshavardhana) - fix: quorum calculation mistake with reduced parity (#10186) (08/03/20) (Harshavardhana) - fix: connection_string should override other params (#10180) (08/03/20) (Harshavardhana) - fix: pull credits in docker from master branch (#10177) (08/02/20) (Harshavardhana) - fix: update and improve zh_CN documentation (#10174) (08/02/20) (้ฃž้›ชๆ— ๆƒ…) - update CREDITS with minio/selfupdate project (07/31/20) (Harshavardhana)