This isn't really installation and configuration but it was related to my protection domain snapshot issue. So, when I ran low on free space, the metadata increased becasue there were still tons of blocks out there to keep track of. So, this combination of low space and threshold breaking metasada size exceeds the preconfigured (metadata) size limit before kicking off automation actions.



I don't really understand these failsafe actions fully but both inline compression and deduplication fingerprinting (I use only performance tier dedup but my true love is compression) are disabled. I am not so sure about compression but I can see deduplication fingerprinting adding to metadata. The kicker, to me, is that space conservation via deduplication and compression is more important when I am low on space.



The recovery from these automatic actions is to free space then call support to re-enable the disabled features. I am waiting for an answer why they do not automatically re-enable and more so, I am asking for a "fix" to this behavior. I prefer self-healing, which is fundamental to the architecture, than manual interference.



So, beware of your metadata sizes and keep in mind the aded affects of snapshots. Have your serial number handy to open a support case to get your space savings powers turned back on.



~ Joe