The type is a bucket prompt, indicating an error message of Invalid party shard count/sulplus shard count given

[opsted24]

I am conducting a test using

mc admin heat -- recursive ts1/ts01
Output is not 100%
 ◓  ts01/240511/ts1.mp4
    0/17 objects; 480 MiB in 1s
    ┌────────┬────┬─────────────────────┐
    │ Green  │ 22 │  95.7% ████████████ │
    │ Yellow │  0 │   0.0%              │
    │ Red    │  0 │   0.0%              │
    │ Grey   │  0 │   0.0%              │
    └────────┴────┴─────────────────────┘

By using `mc admin heal --recursive  resource/ts01 --json` , there are only one error message. The details are as follows

   {
 "status": "success",
 "error": "Invalid parity shard count/surplus shard count given",
 "type": "bucket",
 "name": "ts01/",
 "before": {
  "color": "",
  "offline": 0,
  "online": 1,
  "missing": 0,
  "corrupted": 0,
  "drives": [
   {
    "uuid": "",
    "endpoint": "/data/minio/data",
    "state": "ok"
   }
  ]
 },
 "after": {
  "color": "",
  "offline": 0,
  "online": 1,
  "missing": 0,
  "corrupted": 0,
  "drives": [
   {
    "uuid": "",
    "endpoint": "/data/minio/data",
    "state": "ok"
   }
  ]
 },
 "size": 0
}

But if the type is object, there are no exceptions and the output is

{
 "status": "success",
 "type": "object",
 "name": "ts01/240511/",
 "before": {
  "color": "green",
  "offline": 0,
  "online": 4,
  "missing": 0,
  "corrupted": 0,
  "drives": [
   {
    "uuid": "",
    "endpoint": "http://ts-minio-node-01:9000/data/minio/data",
    "state": "ok"
   },
   {
    "uuid": "",
    "endpoint": "http://ts-minio-node-02:9000/data/minio/data",
    "state": "ok"
   },
   {
    "uuid": "",
    "endpoint": "http://ts-minio-node-03:9000/data/minio/data",
    "state": "ok"
   },
   {
    "uuid": "",
    "endpoint": "http://ts-minio-node-04:9000/data/minio/data",
    "state": "ok"
   }
  ]
 },
 "after": {
  "color": "green",
  "offline": 0,
  "online": 4,
  "missing": 0,
  "corrupted": 0,
  "drives": [
   {
    "uuid": "",
    "endpoint": "http://ts-minio-node-01:9000/data/minio/data",
    "state": "ok"
   },
   {
    "uuid": "",
    "endpoint": "http://ts-minio-node-02:9000/data/minio/data",
    "state": "ok"
   },
   {
    "uuid": "",
    "endpoint": "http://ts-minio-node-node-03:9000/data/minio/data",
    "state": "ok"
   },
   {
    "uuid": "",
    "endpoint": "http://ts-minio-node-04:9000/data/minio/data",
    "state": "ok"
   }
  ]
 },
 "size": 0
}

mc --version

Mini server version: Mini version RELEASE.2024-05-10T01-41-38Z
MC version RELEASE.2024-05-09T17-04-24Z (commit id=fdb36acbb1d793b6cca622a55e6292f0d52309f0)

[klauspost]

mc doesn't understand 0 erasure codes:

mc/cmd/admin-heal-ui.go

Line 54 in e2056fb

if parityShards < 1 || parityShards > 8 || surplusShards > parityShards {

Furthermore this being a prefix there is no healing performed.

[opsted24]

So this is a normal phenomenon, right? I feel very confused because I see that Green is not 100%. The main issue was that there were no issues with the green status. I specifically searched for others and found that the status was 100%. Based on this invalid party shard count/sulplus shard count given error, I specifically contacted relevant personnel who told me it was a service setting issue. But there's no problem with only the bucket type. The main concern is that a node has completely crashed, making it impossible to recover. However, I specifically went to/data/mini/data to check that each node has a related directory, which can be completely ignored, right? It's not that my service configuration is incorrect.