topic Re: Not enough memory error in Microsoft Virtualization Discussions

Not enough memory error

thepunisher — Thu, 05 Jun 2025 06:29:59 GMT

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

+ Get-NaVol

+ ~~~~~~~~~

+ CategoryInfo : InvalidOperation: (aFiLeR:NaController) [Get-NaVol], EONTAPI_ENOMEM

+ FullyQualifiedErrorId : ApiException,DataONTAP.PowerShell.SDK.Cmdlets.Volume.GetNaVol

Re: Not enough memory error

cknight — Wed, 11 Apr 2012 17:27:16 GMT

Can you say (approximately) how many volumes are present?

Re: Not enough memory error

thepunisher — Wed, 11 Apr 2012 17:49:03 GMT

Total of 129 volumes, surprisingly fewer then I would have expected.

Re: Not enough memory error

JGPSHNTAP — Tue, 17 Apr 2012 17:26:54 GMT

If you pipe to out-file do you get same issue?

Re: Not enough memory error

thepunisher — Tue, 17 Apr 2012 17:38:15 GMT

It does, the issue is with the underlying code in the tool kit. Regardless of what you do with the results it always fails.

Re: Not enough memory error

thepunisher — Thu, 10 May 2012 14:21:07 GMT

To get around this error, install the latest version of the toolkit and run; Get-NaVol -Terse

Re: Not enough memory error

cknight — Thu, 10 May 2012 15:00:41 GMT

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.

Re: Not enough memory error

jhorne — Tue, 28 Aug 2012 15:07:24 GMT

I ran into the same issue after hitting about 120 volumes. Using the -Terse switch does work though. Thanks!

Re: Not enough memory error

sneil — Tue, 16 Oct 2012 02:31:52 GMT

I'm running into the same out of memory issue. -Terse work, but what info\data does it not return?

Re: Not enough memory error

cknight — Tue, 16 Oct 2012 23:25:45 GMT

-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

Re: Not enough memory error

bg7777777 — Thu, 26 Mar 2015 18:41:02 GMT

I am getting the same exact error but with get-nadisk | ?{ $_.Status -eq "spare"}

Also trying to query for failed disk. Any suggestions?

Using 3.1.1 toolkit on ontap 8.2.2P1