Active IQ Unified Manager Discussions

Provisioning Manager refuses to provision new qtree in existing volume

arndt
4,305 Views

My customer is using Provisioning Manager (via Ops Mgr 3.8) to provision storage in a multistore environment.  They have a dataset created that contains a single volume and a single qtree within that volume.  When they try to add more qtrees to this volume via the Provision Storage option, Provisioning Manager creates a new volume by the name of <dataset>_1 instead of just adding the qtree to the existing volume named <dataset>.

Here are the dataset specifics:

dfpm dataset list -x nv_dochaload2p_n01ora1_nosnap
Id:                              131661
Name:                            nv_dochaload2p_n01ora1_nosnap
Policy:                         
Provisioning Policy:             ThickNAS_nosnap
Resource Pools:                  eg-nasprod-e02
vFiler:                          prod-ecom-e0057.westlan.com
Description:                     PP06584
Owner:                          
Contact:                        
Volume Qtree Name Prefix:       
DR Capable:                      No
Requires Non Disruptive Restore: No
Export Protocol:                 nfs
NFS Protocol Version:            v3
Disable setuid:                  1
Anonymous Access UID:            0
Read-only Hosts:                 None
Read-write Hosts:                1.1.1.1
Root-access Hosts:               None
Security Flavors:                sys

This is what we see in the conformance log file when we try to provision a new qtree for this dataset:

Apr 21 10:21:01 [dfmserver:DEBUG]: Thread 0xe77f2ba0: ProvisioningChecker: 1 provisioning job(s) found.
Apr 21 10:21:01 [dfmserver:DEBUG]: Thread 0xe77f2ba0: Processing New Storage Request...
Apr 21 10:21:01 [dfmserver:ERROR]: Thread 0xe77f2ba0: Failed to select volume during provisioning
Apr 21 10:21:01 [dfmserver: INFO]: Thread 0xe77f2ba0: Dry run: action: Selected aggregate eg-nasprod-e02:aggr2 for provisioning new volume.

I see the "Failed to select volume during provisioning" message, but no details as to why it failed to select the existing volume for this qtree to be created in.  Any ideas?  Thanks!

Mike

11 REPLIES 11
Public