Below are 2 config blocks. Initial_DataDisk sets a volume on a disk

Hi <a class="user-mention notranslate" data-hovercard-type="organization" data-hoverca

Thanks <a class="user-mention notranslate" data-hovercard-type="organization" data-hov

Unexpected Volume Size does not change InDesiredState value about storagedsc HOT 4 CLOSED

dsccommunity commented on June 12, 2024

Unexpected Volume Size does not change InDesiredState value

from storagedsc.

Comments (4)

ed-vazquez commented on June 12, 2024

Issue may that test-resource does not return false for a mismatch like the other tests.

# Drive size
    if ($Size)
    {
        if ($partition.Size -ne $Size)
        {
            # The partition size mismatches but can't be changed (yet)
            Write-Verbose -Message ( @(
                    "$($MyInvocation.MyCommand): "
                    $($LocalizedData.DriveSizeMismatchMessage `
                        -f $DriveLetter,$Partition.Size,$Size)
                ) -join '' )
        } # if
    } # if

from storagedsc.

PlagueHO commented on June 12, 2024

Hi @VazquezTech - Thank you for reporting this. You are quite correct. This is a known limitation of the resource. This has been on my todo list but I haven't had time to look into it.

This is actually a duplicate of issue #11. It requires the destructive switch (is discussed in #50) to be implemented to allow destructive changes to be made to a disk (in this case resizing the partition).

We choose to return $true when a size mismatch occurs to prevent the Set-TargetResource firing when we can't actually do anything to resolve the size mismatch (yet).

But as this is a duplicate of issue #11, can we close this issue and raise and further discussion in that one?

from storagedsc.

ed-vazquez commented on June 12, 2024

Hi Daniel, Thank you for the prompt response. Please close issue. On Thu, Jan 12, 2017 at 6:21 AM Eduardo Vazquez <[email protected]> wrote:

…

On Thu, Jan 12, 2017 at 12:56 AM Daniel Scott-Raynsford < ***@***.***> wrote: Hi @VazquezTech <https://github.com/VazquezTech> - Thank you for reporting this. You are quite correct. This is a known limitation of the resource. This has been on my todo list but I haven't had time to look into it. This is actually a duplicate of issue #11 <#11>. It requires the destructive switch (is discussed in #50 <#50>) to be implemented to allow destructive changes to be made to a disk (in this case resizing the partition). We choose to return $true when a size mismatch occurs to prevent the Set-TargetResource firing when we can't actually do anything to resolve the size mismatch (yet). But as this is a duplicate of issue #11 <#11>, can we close this issue and raise and further discussion in that one? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#75 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABdc1o9iQ5nJWhHab1XKFGuy7YQ5pSrAks5rRcBwgaJpZM4LhFq6> .

from storagedsc.

PlagueHO commented on June 12, 2024

Thanks @VazquezTech - I'll try and get to the issue #11 when I get time (seem to be very short of it these days).

from storagedsc.

Recommend Projects

Unexpected Volume Size does not change InDesiredState value about storagedsc HOT 4 CLOSED

Comments (4)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent