2011-07-20 06:01 PM
Just wanted to ask as quick question.... I’ve attempted to remove a vfiler and HA pair from DFM as I’ve just decommissioned the storage system. When attempting to remove the viler, I get the an error as shown below.
[root@dfm_server ~]# dfm host list | grep -i <vfiler>
5964 vFiler <vfiler> 10.0.0.1 No
[root@dfm_server ~]# dfm host delete 5964
Error: Can't delete storage system <vfiler> (5964) while managing its 50 primary directories.
I’ve tried this for both physical filers and the single vfiler instance.... in all attempts, I get "Error: Can't delete storage system <vfiler> (5964) while managing its 50 primary directories.". I get the same error in the Web UI as well…. However; when doing this from the NMC, I was able to remove the vfiler/filer without any issue.
In this specific DFM instance, I use only Alerting and Performance Advisor…. I have another DFM instance for Prot/Prov Mgr…. however; on both DFM server, I get the exact same error about the “50 Primary directories”.
Can anyone tell me why I was able to delete from the NMC but not the WebUI or DFM CLI? As well, where would these ’50 primary directories’ be located within DFM for me to look at so I know to check next time.
Thanks a lot!
2011-07-21 04:02 AM
What about the filer? I think Scott says he was able to delete the the filers as well from NMC but not from cmd or Web UI?
2011-07-21 06:01 AM
This behavior is expected even though its not consistent between cli and NMC.
The NMC delete of host was added in 4.0.1 by bug 255202
You are hitting bug 433740. If you like to have consistent behavior pls add your case to this bug.
Thanks to Kevin Ryan,
2011-07-21 09:08 AM
From the CLI you can use "dfbm primary dir list <vfiler-name-or-id>" to get a list of SnapVault primary qtrees on that vfiler, then use "dfbm primary dir relinquish" to release them. There may be a way to do this via the web GUI but I don't remember how off the top of my head.
What's going on is DFM has discovered some SnapVault relationships coming from that filer or vfiler unit. We don't let you mark the filer/vfiler as deleted as long as we think those relationships exist. Relinquishing them tells DFM it's OK to delete the vfiler.