Subscribe
Accepted Solution

Provisioning Manager volume state error

Hi all,

I'm new to Provisioning Manager but I've managed to get my head around the relationships between policies, storage services and the like, enough to try provisioning. When I attempt to provision a volume for NFS export using a Provisioning Policy based on a Storage Service, the filer creates the QTree and the volume (I see this on console output) but then Provisioning Manager throws up an error of "WARNING: Volume state transition is in progress" and the console shows the filer destroying the volume and QTree.

Could anyone please advise what could be causing this error?

Thanks in advance!

Provisioning Manager volume state error

Can you post the details of the job,

dfpm job detail <job id > ?

Also how many concurrent provisioning job request did you make ?

How many backup jobs where running if any.

Regards

adai

Provisioning Manager volume state error

If dedupe is enabled in the Provisioning policy then this situation might arise. If some parallel tasks like setting quota on qtree, volume resize take place when dedupe was being enabled on the volume this state might come.

Please see if you can provision by disabling dedupe in the policy; we can narrow down the problem.

Thanks

Tanmoy

Provisioning Manager volume state error

Hi, thanks for getting back to me. Where do I enter the command "dfpm job detail" please?

I made 1 concurrent provisioning job request and no backup jobs were running.

Provisioning Manager volume state error

Found where to enter the dfpm command, here's the output as requested.

C:\Users\Administrator>dfpm job detail 25

Job Id:                    25
Job State:                 completed
Job Description:           test
Job Type:                  provision_member
Job Status:                failure
Dataset Name:              CORP_DSWK_OS
Dataset Id:                789
Object Name:               CORP_DSWK_OS
Object Id:                 789
Started Timestamp:         02 Jun 2011 15:03:29
Abort Requested Timestamp:
Completed Timestamp:       02 Jun 2011 15:03:31
Submitted By:              administrator
Provisioning Policy Id:    744
Provisioning Policy Name:  CORP_FASWK_VMW_NFS

Job progress messages:

Event Id:      202
Event Status:  normal
Event Type:    job-start
Job Id:        25
Timestamp:     02 Jun 2011 15:03:29
Message:
Error Message:

Event Id:      203
Event Status:  normal
Event Type:    volume-create
Job Id:        25
Timestamp:     02 Jun 2011 15:03:30
Message:       Provision flexible volume of size 500 GB with space guarantee set
to "file"
Error Message:
Volume Id:     794
Volume Name:   CORP-FASWK-SAS:/CORP_DSWK_OS_7

Event Id:      204
Event Status:  normal
Event Type:    qtree-create
Job Id:        25
Timestamp:     02 Jun 2011 15:03:30
Message:       Successfully provisioned qtree test on volume 'CORP-FASWK-SAS:/CO
RP_DSWK_OS_7'(794)
Error Message:
Qtree Id:      797
Volume Id:     794
Volume Name:   CORP-FASWK-SAS:/CORP_DSWK_OS_7
Qtree Name:    CORP-FASWK-SAS:/CORP_DSWK_OS_7/test

Event Id:        205
Event Status:    normal
Event Type:      nfsexport-create
Job Id:          25
Timestamp:       02 Jun 2011 15:03:30
Message:         Export qtree QtreeToBeProvision-CORP-DSWK-OS over NFS.
Error Message:
Qtree Id:        797
Qtree Name:      CORP-FASWK-SAS:/CORP_DSWK_OS_7/test
NFS Export Path: CORP-FASWK-SAS:/vol/CORP_DSWK_OS_7/test

Event Id:      206
Event Status:  normal
Event Type:    volume-dedupe-enable
Job Id:        25
Timestamp:     02 Jun 2011 15:03:30
Message:       Successfully enabled deduplication on flexible volume 'CORP-FASWK
-SAS:/CORP_DSWK_OS_7'(794)
Error Message:
Volume Id:     794
Volume Name:   CORP-FASWK-SAS:/CORP_DSWK_OS_7

Event Id:      207
Event Status:  error
Event Type:    volume-dedupe-schedule-set
Job Id:        25
Timestamp:     02 Jun 2011 15:03:30
Message:       Setting deduplication schedule 'auto' on flexible volume 'VolToBe
Provision:CORP-DSWK-OS' (20)
Error Message: CORP-FASWK-SAS: Volume state transition is in progress
Volume Id:     794
Volume Name:   CORP-FASWK-SAS:/CORP_DSWK_OS_7

Event Id:       208
Event Status:   normal
Event Type:     volume-option-set
Job Id:         25
Timestamp:      02 Jun 2011 15:03:30
Message:        Successfully set volume options.
Error Message:
Volume Id:      794
Volume Name:    CORP_DSWK_OS_7
Volume Options: convert_ucode=on,create_ucode=on

Event Id:      209
Event Status:  normal
Event Type:    snapshot-reserve-resize
Job Id:        25
Timestamp:     02 Jun 2011 15:03:30
Message:       Successfully set snap reserve for volume 'CORP-FASWK-SAS:/CORP_DS
WK_OS_7'(794) to 0 percent.
Error Message:
Volume Id:     794
Volume Name:   CORP-FASWK-SAS:/CORP_DSWK_OS_7

Event Id:      210
Event Status:  normal
Event Type:    quota-set
Job Id:        25
Timestamp:     02 Jun 2011 15:03:31
Message:       Set Tree Quota = 500 GB
Error Message:
Qtree Id:      797
Qtree Name:    CORP-FASWK-SAS:/CORP_DSWK_OS_7/test
Tree Quota:    500 GB

Event Id:      211
Event Status:  error
Event Type:    job-end
Job Id:        25
Timestamp:     02 Jun 2011 15:03:31
Message:       Job Failed
Error Message: CORP-FASWK-SAS: Volume state transition is in progress

Provisioning Manager volume state error

Hi Tanmoy,

I've removed dedupe from the Provisioning policy and now successfully provisioned a few times, very useful answer; thank you!

Is this a known "bug" and something likely to be resolved or will be most likely have to use this workaround all the time?

Provisioning Manager volume state error

I now have one last question, slightly related. Every failed attempt results in a new QTree with an ascending numeric ID on the end. For example, if I now successfully provision my first volume, it will be appended with _7 (eg, TEST_7 is my first successful creation). Is there a way to reset this counter so I can cleanly provision my QTrees and Volumes please?

Provisioning Manager volume state error

you are hitting bug 496605, please raise a case and attach your call_rec to this bug

Regards

adai

Provisioning Manager volume state error

destroy the dataset and create it new.And start the provisioing new.

As long as the dataset remains, the counter keep increasing, there is noway to reset it.

Regards

adai

Provisioning Manager volume state error

Hello Adai,

We've raised case # 2002256473 which we will attach as requested, many thanks.

Regarding the incrementing counter, I tried to remove the dataset and volumes, I recreated the dataset with the same name as previous and the counter "picked up where it left off", did not begin at 1 again. Could this be another bug or is this expected when the new dataset is named the same as the original?

Thanks.