`bm admin heal`

Description

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

bm admin heal is resource intensive and typically not required as a manual process, even after drive failures or corruption events.

As a part of normal operations, Buckit:

automatically heals objects damaged by silent bit rot corruption, drive failure, or other issues on each POST or GET operation.
performs periodic background object healing using the scanner.
aggressively heals objects after drive replacement.

Refer to Object Healing for more details on how Buckit heals objects.

Use bm admin on Buckit Deployments Only

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

Syntax

bm admin heal has the following syntax:

bm admin heal [FLAGS] TARGET             \
                      [--all-drives, -a] \
                      [--force]          \
                      [--verbose, -v]

bm admin heal supports the following arguments:

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 Buckit deployment as the prefix for the path. For example:

bm 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.

--all-drives, -a: Optional
Select all drives and show verbose information.

--force: Optional
Disables warning prompts.

--verbose, -v: Optional
Show information about offline and faulty healing drives.

Healing Colors

Some versions of Buckit used a color key as a way to differentiate objects with different healing statuses.

The color meaning has been updated.

Green indicates the bucket is healthy.
Yellow indicates the bucket requires healing on one or more drives.
Red indicates one or more drives are unhealthy.
Grey indicates an indeterminate healing state.