VMAX3 all Flash creates by itself pools with devs config in uknown state

[kikoguanabakoa]

hi

does any one know why a new VMAX3 all flash creates by itself pools with devs config in unknown state,

Regards

[SKT2]

this is not ideal; please open a case with support.

[Jianyun]

yes suggest to have a SR. VMAX3 should be checked by PSE. And if there is more detailed log then we can take a look as well.

[kikoguanabakoa]

Thanks

Please take a look at this output

[KW160]

These pools are used for data compression on VMAX All Flash. They will be populated with data once compression is enabled on a storage group. Please consult this White Paper for additional details: https://www.emc.com/collateral/white-papers/h15393-vmax-all-flash-adaptive-compression-engine.pdf

[Jianyun]

then it's no worry. These pools are "compression pools", and right now the compression is not activated yet so only 128KB pool (this 128KB pool has same track size as original which means no compression) is used, you may see the compression ratio is 1.0:1.

The default compression pools are: 16K, 32K, 40K, 48K, 56K, 64K, 72K and 128K. Once the exact pool is used, the device config will be shown.

[Jianyun]

here it's an example while some compression pools are used.

[Ayrton_Senna1]

Totally unrelated, Just curious to know, what is the ENCAPSPOOL listed in your output.

[Jianyun]

this is "Encapsulated" pool, it's for external connection which can be Data Domain connection etc.