NOTE

If this case is urgent, please subscribe to Subnet so that our 24/7 support team may help you faster.

We have deployed Minio using the minio/minio container image on Azure Container Apps (a sort of managed kubernetes). Storage is provided by a mounted volume backed by Azure Files Storage.

We only have a few videos on the one bucket we created for a LMS and the LMS is shutdown (nothing accessing MINIO). We see relatively high transactions to the disk which is causing quite a usage bill if we operate like this in the long term.

Over the last hour, with nothing calling the MINIO api, the system has generated 80k disk access transactions.

We have _MINIO_DRIVE_ACTIVE_MONITORING=off in the environment, though not sure HEALING is running as querying with mc admin config get yields that healing is deactivated on this single drive single node instalaltion.

Expected Behavior

Would expect the system to not continuously try and read/write data to the disk

Current Behavior

API not exposed and yet 80k disk transactions done.

Possible Solution

I don't know if caching would be appropriate, or just minimising disk accesses.

Steps to Reproduce (for bugs)

Deploy MINIO to Azure Container apps with a volume backed by Azure Files Storage.

Context

Cost of operating MINIO

Regression

No

Your Environment

uname - a : Linux host12345-wft7b 5.15.176.3-3.cm2 #1 SMP Tue Mar 4 02:02:18 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux