2012-04-11 09:32 AM
I am trying to run the get-navol command against one of our snapvault destinations. I have run this against this filer in the past and haven't had problems. The only thing that I can think if that have changed since the last time I successfully got this to run was the aggregates on the filer have been converted to 64 bit and I have upgraded the tool kit. Is this an environment issue (meaning my machines configuration) or an issue with the toolkit?
PS C:\Scripts> Get-NaVol
Get-NaVol : Not enough memory for reply value, but command completed successfully
At line:1 char:1
+ CategoryInfo : InvalidOperation: (aFiLeR:NaController) [Get-NaVol], EONTAPI_ENOMEM
+ FullyQualifiedErrorId : ApiException,DataONTAP.PowerShell.SDK.Cmdlets.Volume.GetNaVol
2012-05-10 08:00 AM
Thanks for confirming that works. Get-NaVol returns a large amount of info, much of it rarely needed in a volume context; that was apparently leading to the out-of-memory condition in Data ONTAP's API handler. -Terse omits some of the extra data, and the resulting packets are much smaller.
2012-10-16 04:25 PM
-Terse omits a number of info types, such as autosize info, RAID group info, and autodelete info. Just try these two commands and compare the differences:
Get-NaVol vol0 | Format-Custom
Get-NaVol vol0 -Terse | Format-Custom