Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
10 REPLIES 10
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you say (approximately) how many volumes are present?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Total of 129 volumes, surprisingly fewer then I would have expected.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you pipe to out-file do you get same issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It does, the issue is with the underlying code in the tool kit. Regardless of what you do with the results it always fails.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To get around this error, install the latest version of the toolkit and run; Get-NaVol -Terse
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm running into the same out of memory issue. -Terse work, but what info\data does it not return?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
-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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I ran into the same issue after hitting about 120 volumes. Using the -Terse switch does work though. Thanks!
