Description mc admin object info displays a summary of part and shard information about a specified object. The output includes information for each part or shard of the object, including: Part number Pool number Node Erasure set Drive Filename Size By default, the output uses a set of gridded blocks to indicate the parts of object. Colors indicate the status of the specific part.

Basic mathematical constants.

The mc find command supports searching for objects on a AIStor deployment. You can also use the command to search for files on a filesystem. Syntax Example The following command searches for all objects matching the specified pattern in the mydata bucket on the myminio AIStor deployment:

The mc admin user rm command removes a AIStor user on the target AIStor deployment. The mc admin user remove command has equivalent functionality to mc admin user rm. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command removes user myuser on the myminio AIStor deployment:

none deflate 72 8 8 8 PixelInterleaved 0.35273367 width=72, height=72, bitDepth=8, colorType=RGB, compressionMethod=deflate, filterMethod=adaptive, interlaceMethod=none RGB 634 8 8 8 72 1 pixelsPer...

Linux-specific extensions to primitives in the `std::fs` module.

Description The mc admin trace command displays API operations occurring on the target AIStor deployment. Example Example Use mc admin trace to monitor API operations on a AIStor deployment:

The AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). The batch jobs run directly on the MinIO deployment to take advantage of the server-side processing power without constraints of the local machine where you run the MinIO Client. A batch file defines one job task. Once started, the AIStor server starts processing the batch job. Time to completion depends on the resources available to the deployment.

AIStor supports scaling deployments by expanding or decomissioning server pools. Ideally, deployments should plan for 3 years of data growth at installation.

Linux-specific extensions to primitives in the `std::process` module.