Hi Dominic Marsh,
Apologies for the inconvenience
I understand how frustrating it can be to deal with such large meta.edb files.
Possible causes:
High file count: Meta.edb files store metadata for all files, including layer files. A large number of files can increase the metadata significantly.
Frequent file changes: Frequent file changes can increase the size of the metadata database while keeping track of these changes.
Sync errors: Sometimes Sync problems or errors can cause metadata files to grow unexpectedly.
Suggestions:
Checking for synchronization errors: Check for synchronization errors using the Azure portal or event logs on the server. Fixing this error can sometimes reduce the size of the meta.edb file.
Optimal file organization: Reducing the number of files or reorganizing your file shares can help manage metadata file size.
Modify Cache Settings: You can adjust the MaxCacheSize and MaxCacheAge settings to control how much data is cached locally.
Routine maintenance: Perform routine maintenance tasks such as parsing the meta.edb file and ensure that the server has the right resources.
To fix:
Verify the service status: Verify that the Storage Sync Agent service (FileSyncSvc) is running on the server.
Run diagnostics: Use the Debug-StorageSyncServer PowerShell cmdlet to diagnose common issues with the Azure File Sync server.
Review notes: Collect and review notes to identify any underlying problems. You can use the AFSDiag.ps1 script for advanced analysis.
Please let me know if there is any other information needed.