Skip to content

Latest commit

 

History

History
10 lines (8 loc) · 712 Bytes

minio_cannot_serve_some_content.md

File metadata and controls

10 lines (8 loc) · 712 Bytes

MinIO Cannot Serve Some Content

Sometimes unexpected error from MinIO occur whether it's because of the filesystem was broken or MinIO failed to start the service (Disk usage full). This will cause a 504 Gateway Timeout issue on the client side where minio is not running properly

Problem solving:

  • Inside MinIO data (ex: /data/minio), there is some directories from bucket's cache and reserved system .minio.sys
  • All we need to do is remove or rename all bucket's cache directories
  • This will makes MinIO run likes a fresh server or migrated from another instance

This workaround is to run MinIO server like migrated from another instance by copying .minio.sys directory between MinIO instance