Excessive memory usage occurs and Vxio, Vxip, Vxis or Vxit memory pool tags show high memory counts when an InfoScale server is under heavy I/O
Article ID: 100033877
Updated On:
Description
Workaround
To work around this issue, disable TRIM. Do not disable TRIM if Solid State Drives (SSDs) are not being used. Contact Veritas Technical Support for further assistance if SSDs are configured.To disable TRIM support in Windows, type the following at a command prompt, and press enter:
fsutil behavior set DisableDeleteNotify 1
To enable TRIM support in Windows, type the following at command prompt, and press enter:
fsutil behavior set DisableDeleteNotify 0
A reboot is not required.
Cause
When TRIM is enabled (by default), the memory utilization continues to increase.
PoolMon.exe may show high memory counts for Vxio, Vxip, Vxis and Vxit.
During heavy I/O read-write locking and file delete operations affect I/O performance. It has also been observed that while not rising to what might be determined as excessive usage, that PoolMon.exe may show increasing memory counts for Vxio, Vxip, Vxis and Vxit when monitored over an interval of a few hours.
Heavy I/O in this scenario on systems with thin reclamation devices may also be caused by operations on the thin reclamation devices as part of the reclamation process.
PoolMon.exe may show high memory counts for Vxio, Vxip, Vxis and Vxit.
Vxio Nonp 259 190 69 17816464 258209
Vxio Paged 1 0 1 144 144
Vxip Nonp 2273953 610359 1663594 239557536 144 <-- 230MB
Vxiq Nonp 1071108 1071018 90 24480 272
Vxir Nonp 106459 106429 30 12000 400
Vxis Nonp 1663465 0 1663465 878309520 528 <-- 837MB
Vxit Nonp 1663464 0 1663464 1091232384 656 <-- 1040MB
Vxio Paged 1 0 1 144 144
Vxip Nonp 2273953 610359 1663594 239557536 144 <-- 230MB
Vxiq Nonp 1071108 1071018 90 24480 272
Vxir Nonp 106459 106429 30 12000 400
Vxis Nonp 1663465 0 1663465 878309520 528 <-- 837MB
Vxit Nonp 1663464 0 1663464 1091232384 656 <-- 1040MB
During heavy I/O read-write locking and file delete operations affect I/O performance. It has also been observed that while not rising to what might be determined as excessive usage, that PoolMon.exe may show increasing memory counts for Vxio, Vxip, Vxis and Vxit when monitored over an interval of a few hours.
Heavy I/O in this scenario on systems with thin reclamation devices may also be caused by operations on the thin reclamation devices as part of the reclamation process.
Resolution
A hotfix exists for this issue, please contact Veritas Support Solutions for more information on obtaining this hotfix.
Issue/Introduction
During heavy I/O, the memory utilization increases and the server becomes unresponsive.
When using Solid State Drive (SSD) devices with TRIM-based reclamation, the following issues may be observed:
When using Solid State Drive (SSD) devices with TRIM-based reclamation, the following issues may be observed:
- When the operating system processes the TRIM request, application I/O performance is reduced.
- When multiple file delete operations are performed, the memory leak may occur.
Additional Information
ETrack: 3917779
Was this article helpful?
Yes
No
Powered by
