571f188a4e
##
We are going to make the following changes to the Object Store docs as
part of a larger QC/Content pass:
### Left Navigation
We want to modify the left navigation flow to be a natural progression
from a basic setup to more advanced.
For example:
- Core Concepts
- Deployment Architecture
- Availability and Resiliency
- Erasure Coding and Object Healing
- Object Scanner
- Site Replication and Failover
- Thresholds and Limits
- Installation
- Deployment Checklist
- Deploy MinIO on Kubernetes
- Deploy MinIO on Red Hat Linux
- Deploy MinIO on Ubuntu Linux
- Deploy MinIO for Development (MacOS, Windows, Container)
- Security and Encryption (Conceptual Overview)
- Network Encryption (TLS) (Conceptual overview)
- Enable Network Encryption using Single Domain
- Enable Network Encryption using Multiple Domains
- Enable Network Encryption using certmanager (Kubernetes only)
- Data Encryption (SSE) (Conceptual overview)
- Enable SSE using AIStor Key Management Server
- Enable SSE using KES (Summary page + linkouts)
- External Identity Management (Conceptual Overview)
- Enable External Identity management using OpenID
- Enable External Identity management using AD/LDAP
- Backup and Recovery
- Create a Multi-Site Replication Configuration
- Recovery after Hardware Failure
- Recover after drive failure
- Recover after node failure
- Recover after site failure
- Monitoring and Alerts
- Metrics and Alerting (v3 reference)
- Monitoring and Alerting using Prometheus
- Monitoring and Alerting using InfluxDB
- Monitoring and Alerting using Grafana
- Metrics V2 Reference
- Publish Server and Audit Logs to External Services
- MinIO Healthcheck API
The Administration, Developer, and Reference sections will remain as-is
for now.
http://192.241.195.202:9000/staging/singleplat/mindocs/index.html
# Goals
Maintaining multiple platforms is getting to be too much, and based on
analytics the actual number of users taking advantage of it is minimal.
Furthermore, the majority of traffic is to installation pages.
Therefore we're going to try to collapse back into a single MinIO Object
Storage product, and use simple navigation and on-page selectors to
handle Baremetal vs Kubernetes.
This may also help to eventually stage us to migrate to Hugo + Markdown
---------
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Co-authored-by: Rushan <rushenn@minio.io>
Co-authored-by: rushenn <rushenn123@gmail.com>
6.9 KiB
mc stat
minio
Table of Contents
mc stat
Syntax
The mc stat command
displays information on objects in a MinIO bucket, including object
metadata. You can also use it to retrieve bucket metadata.
You can use mc stat
against the local filesystem to produce similar results to the
stat commandline tool.
EXAMPLE
The following command displays information on all objects in the
mydata bucket on the myminio MinIO
deployment:
mc stat --recursive myminio/mydataSYNTAX
The command has the following syntax:
mc [GLOBALFLAGS] stat \
[--enc-c "value"] \
[--no-list] \
[--recursive] \
[--rewind "string"] \
[--versions] \
[--version-id "string"]* \
ALIAS [ALIAS ...]mc stat --version-id is mutually exclusive with
multiple parameters. See the reference documentation for more
information.
Parameters
ALIAS
The alias <alias> of a MinIO deployment and the full
path to the object for which to retrieve detailed information. For
example:
mc stat myminio/mybucket/myobject.txtYou can specify multiple objects on the same or different MinIO deployments:
mc stat myminio/mybucket/myobject.txt myminio/mybucket/myobject.txtIf specifying the path to a bucket or bucket prefix, you
must include the mc stat --recursive flag:
mc stat --recursive myminio/mybucket/For retrieving information on a file from a local filesystem, specify the full path to that file:
mc stat ~/data/myobject.txt--no-list
Disable all LIST operations if the target does not
exist.
--recursive, r
Recursively mc stat
the contents of the MinIO bucket specified to ~mc stat ALIAS.
--rewind
--versions
Use ~mc stat --versions and ~mc stat --rewind together
to remove all object versions which existed at a specific point in
time.
--version-id, vid
Mutually exclusive with any of the following flags:
~mc stat --versions~mc stat --rewind~mc stat --recursive
Global Flags
Examples
Display Object Details
The following example displays details of the object
myfile.txt in the bucket mybucket:
mc stat myminio/mybucket/myfile.txtThe output resembles the following:
Name : myfile.txt
Date : 2024-07-16 15:40:02 MDT
Size : 6.0 KiB
ETag : 3b38f7b05a0c42acdc377e60b2a74ddf
Type : file
Metadata :
Content-Type: text/plain You can specify more than one object by adding multiple paths:
mc stat myminio/mybucket/file1.txt myminio/yourbucket/file2.txtTo display detail for all objects in a bucket, use ~mc stat --recursive. The
following example displays details for all objects in bucket
mybucket:
mc stat --recursive myminio/mybucketThe output resembles the following:
Name : file1.txt
Date : 2024-07-16 15:40:02 MDT
Size : 6.0 KiB
ETag : 3b38f7b05a0c42acdc377e60b2a74ddf
Type : file
Metadata :
Content-Type: text/plain
Name : file2.txt
Date : 2024-07-26 10:45:19 MDT
Size : 6.0 KiB
ETag : 3b38f7b05a0c42acdc377e60b2a74ddf
Type : file
Metadata :
Content-Type: text/plainDisplay Bucket Details
The following example displays information about the bucket
mybucket on the myminio MinIO deployment:
mc stat myminio/mybucketThe output resembles the following:
Name : mybucket
Date : 2024-07-26 10:56:43 MDT
Size : N/A
Type : folder
Properties:
Versioning: Un-versioned
Location: us-east-1
Anonymous: Disabled
ILM: Disabled
Usage:
Total size: 6.0 KiB
Objects count: 1
Versions count: 0
Object sizes histogram:
1 object(s) BETWEEN_1024B_AND_1_MB
1 object(s) BETWEEN_1024_B_AND_64_KB
0 object(s) BETWEEN_10_MB_AND_64_MB
0 object(s) BETWEEN_128_MB_AND_512_MB
0 object(s) BETWEEN_1_MB_AND_10_MB
0 object(s) BETWEEN_256_KB_AND_512_KB
0 object(s) BETWEEN_512_KB_AND_1_MB
0 object(s) BETWEEN_64_KB_AND_256_KB
0 object(s) BETWEEN_64_MB_AND_128_MB
0 object(s) GREATER_THAN_512_MB
0 object(s) LESS_THAN_1024_BCount of Objects in a Bucket
To show the number of objects in a bucket, use --json <mc.--json> and extract the value
of objectsCount with a JSON parser:
The following example uses the jq utility:
mc stat myminio/mybucket --json | jq '.Usage.objectsCount'