MinIO Server Documentation
Customer Login
Product
MinIO Enterprise Object Store
Overview Architecture
Features
MinIO for Public Cloud
AWS GCS Azure
MinIO for Private Cloud
OpenShift SUSE Rancher Tanzu
MinIO for Baremetal
Linux and Windows
Determine your raw and usable capacity Erasure Code Calculator MinIO's Recommended Hardware Configuration Reference Hardware
Solutions
AI Storage Object storage is powering the AI revolution. Learn how MinIO is leading the AI storage market through performance at scale. Modern Datalakes Modern, multi-engine datalakes depend on object stores that deliver performance at scale. Learn more about this core MinIO use case. Hybrid Cloud Effective multi-cloud storage strategies rely on utilizing architecture and tools that can function seamlessly across diverse environments. Equinix Repatriate your data onto the cloud you control with MinIO on Equinix to lower costs while maintaining public cloud adjacency. Splunk Find out how MinIO is delivering performance at scale for Splunk SmartStores. Snowflake Query and analyze multiple data sources, including streaming data, residing on MinIO with the Snowflake Data Cloud. No need to move the data, just query using SnowSQL. SQL Server Discover how to pair SQL Server 2022 with MinIO to run queries on your data on any cloud - without having to move it. HDFS Migration Modernize and simplify your big data storage infrastructure with high-performance, Kubernetes-native object storage from MinIO. VMware Discover how MinIO integrates with VMware across the portfolio from the Persistent Data platform to TKG and how we support their Kubernetes ambitions. Veeam Learn how MinIO and Veeam have partnered to drive performance and scalability for a variety of backup use cases. Commvault Learn how Commvault and MinIO are partnered to deliver performance at scale for mission critical backup and restore workloads. Integrations Browse our vast portfolio of integrations.
Community
GitHub Join our GitHub open source community: explore, experiment, ask questions, and contribute. Slack Channel The MinIO Community Slack provides an open forum for discussing topics related to MinIO. All support is provided on a best-effort basis.
Docs Blog Resources Training Partner Pricing Download

Documentation

MinIO Object Storage for Linux

mc admin heal

Description

The mc admin heal command scans for objects that are damaged or corrupted and heals those objects.

mc admin heal is resource intensive and typically not required even after drive failures or corruption events. Instead, MinIO automatically heals objects damaged by silent bit rot corruption, drive failure, or other issues on POST/GET. MinIO also performs periodic background object healing.

Use mc admin on MinIO Deployments Only

MinIO does not support using mc admin commands with other S3-compatible services, regardless of their claimed compatibility with MinIO deployments.

Syntax

mc admin heal has the following syntax:

mc admin heal [FLAGS] TARGET

mc admin heal supports the following argument:

TARGET

Required

The full path to the bucket or bucket prefix on which the command should perform object healing. Specify the alias of a configured MinIO deployment as the prefix for the path. For example:

mc admin heal play/mybucket/myprefix

If the TARGET bucket or bucket prefix has an active healing scan, the command returns the status of that scan.

Deprecated Arguments

The following command flags have been deprecated and should only be used under guidance from MinIO Engineers in association with a SUBNET ticket.

  • --scan

    The type of scan to perform. Specify one of the following supported scan modes:

    • normal (default)

    • deep

  • --recursive, r

    Recursively scans for objects in the specified bucket or bucket prefix.

  • --dry-run

    Inspects the TARGET bucket or bucket prefix, but does not perform any object healing.

  • --force-start, f

    Force starts the healing process.

  • --force-stop, s

    Force stops the healing sequence.

  • --remove

    Removes dangling objects and data directories in the healing process not referenced by the metadata on a per-drive basis.

Healing Output Color Key

Originally, the healing mechanism output a table that used a Green-Yellow-Red-Gray color key to attempt to differentiate the status of objects in healing. These colors have been deprecated in favor of more detailed healing metrics available at the cluster level.

The following table describes the intent of each of the deprecated color keys.

Green

Healthy, the object has all data and parity shards available as required to serve the object

Yellow

Healing, the object is still in the process of healing, and there are sufficient data or parity shards available to complete the healing

Red

Unhealthy, the object has lost one or more shards and requires healing

Grey

Unrecoverable, the object has lost too many data and/or parity shards and cannot be healed or recovered
This work is licensed under a Creative Commons Attribution 4.0 International License. 2020-Present, MinIO, Inc. Creative Commons License