MongoDB Container persisted to Azure Blob (Container) Storage get corrupted

Question

Hi,

I am using “mongo:noble” container for my AKS project, the container is persisted to Azure Container Storage ( Blob storage ). It was working fine till last month, but then suddenly when the AKS was loading the MongoDB container it started failing and complaining that the database is corrupted.

PersistentVolume class used: “azureblob-fuse-premium” csi driver: blob.csi.azure.com storage capacity: 100Gi ( actually used like 10gb )

attaching the log from the MongoDB

{"t":{"$date":"2025-04-07T12:55:34.218+00:00"},"s":"I", "c":"CONTROL", "id":23285, "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}

{"t":{"$date":"2025-04-07T12:55:34.221+00:00"},"s":"I", "c":"CONTROL", "id":5945603, "ctx":"main","msg":"Multi threading initialized"}

{"t":{"$date":"2025-04-07T12:55:34.221+00:00"},"s":"I", "c":"NETWORK", "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set at least one of the related parameters","attr":{"relatedParameters":["tcpFastOpenServer","tcpFastOpenClient","tcpFastOpenQueueSize"]}}

{"t":{"$date":"2025-04-07T12:55:34.223+00:00"},"s":"I", "c":"NETWORK", "id":4915701, "ctx":"main","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":25},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":25},"outgoing":{"minWireVersion":6,"maxWireVersion":25},"isInternalClient":true}}}

{"t":{"$date":"2025-04-07T12:55:34.223+00:00"},"s":"I", "c":"TENANT_M", "id":7091600, "ctx":"main","msg":"Starting TenantMigrationAccessBlockerRegistry"}

{"t":{"$date":"2025-04-07T12:55:34.223+00:00"},"s":"I", "c":"CONTROL", "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1,"port":27017,"dbPath":"/data/mongoaz","architecture":"64-bit","host":"db-8677c79db9-pm67q"}}

{"t":{"$date":"2025-04-07T12:55:34.223+00:00"},"s":"I", "c":"CONTROL", "id":23403, "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"8.0.6","gitVersion":"80f21521ad4a3dfd5613f5d649d7058c6d46277f","openSSLVersion":"OpenSSL 3.0.13 30 Jan 2024","modules":[],"allocator":"tcmalloc-google","environment":{"distmod":"ubuntu2404","distarch":"x86_64","target_arch":"x86_64"}}}}

{"t":{"$date":"2025-04-07T12:55:34.223+00:00"},"s":"I", "c":"CONTROL", "id":51765, "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Ubuntu","version":"24.04"}}}

{"t":{"$date":"2025-04-07T12:55:34.223+00:00"},"s":"I", "c":"CONTROL", "id":21951, "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"net":{"bindIp":"*"},"storage":{"dbPath":"/data/mongoaz"}}}}

{"t":{"$date":"2025-04-07T12:55:34.303+00:00"},"s":"I", "c":"STORAGE", "id":22270, "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"/data/mongoaz","storageEngine":"wiredTiger"}}

{"t":{"$date":"2025-04-07T12:55:35.911+00:00"},"s":"I", "c":"CONTROL", "id":31445, "ctx":"initandlisten","msg":"Frame","attr":{"frame":{"a":"55EBF17C36E8","b":"55EBEB9BC000","o":"5E076E8","s":"wiredtiger_open","s+":"26F8"}}}

`{"t":{"$date":"2025-04-07T12:55:35.911+00:00"},"s":"I", "c":"CONTROL", "id":31445, "ctx":"initandlisten","msg":"Frame","attr":{"frame":{"a":"55EBF1758201","b":"55EBEB9BC000","o":"5D9C201","s":"ZN5mongo18WiredTigerKVEngine15_openWiredTigerERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8","C":"mongo::WiredTigerKVEngine::_openWiredTiger(std::__cxx11::basic_string

Answer 1

Hi Arnoldas,

Thank you for reaching out and sharing your question on the Q&A portal. I appreciate the detailed logs and context you provided—it’s very helpful for troubleshooting.

From the logs, it looks like the MongoDB container is encountering a segmentation fault (Signal: 11) when trying to read data from the Azure Blob Storage-backed persistent volume. This could indeed be related to configuration or compatibility issues between MongoDB’s WiredTiger storage engine and the Azure Blob FUSE driver.

A few things to check:

• Ensure the azureblob-fuse-premium storage class is configured with the recommended settings for MongoDB workloads. Blob FUSE may not always handle frequent small I/O operations as efficiently as MongoDB expects.

Verify the MongoDB version (8.0.6) is fully compatible with the underlying OS and storage driver. Sometimes, edge cases arise with specific combinations.

Check if the corruption persists when using a different storage class (e.g., Azure Disk) temporarily to isolate the issue.

Let me know if you’d like to dive deeper into any of these areas. Happy to help further!

Best regards,

Alex

P.S. If my answer helps you, please Accept my answer.