Daniel Scott-Raynsford

Hi @briefcase-Wanker (Inbetweeners fan :grin:), this does look like a bug. It does look like it could be similar to this issue: https://github.com/dsccommunity/StorageDsc/issues/80 And it looks like I wasn't able...

Hi @briefcase-Wanker - ah right, this explains why the error occurs: It looks like this is caused by clustering because there are three partition objects with G: drive assigned. The...

Additional Note: I can't release new versions of this module until I've updated this to the new CI/CD pipeline. This is #223

Hi @Fiander - thank you for raising this. That is really useful information. I'm thinking we could put this into a new support function `Get-PartitionSupportedSizeAvoidDefrag` (although I'm not a fan...

@TaylorTWBrown - does this occur outside DSC and which version of WS 2019 is this on?

I have noticed this during integration tests and should be resolved if possible - although it doesn't seem to cause a failure. It should be easy enough to fix using...

Hi @ndoody - thanks for raising this. Are you possibly able to post the verbose logs from running the DSC config here (minus any identifiable info)?

Thanks @ndoody - I'm having a go at replicating this now. Hopefully I have an idea where this might occur.

Hi @ndoody - *facepalm* from me - I've realized what is happening here. The issue is that each the Disk resource uses the Size to determine if it should create...

Thinking about this further, I think we need some better examples and documentation of this behavior until we have a good way of resolving it.