Skip to main content
NetApp Knowledge Base

IO error(Event ID 136) observed on host end when volume metadata was reset

  1. Last updated
  2. Save as PDF
Views:
98
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
san
Last Updated:

Applies to

  • Microsoft Windows Server
  • Snapmirror
  • FC

Issue

  • When a snapmirrored LUN is presented to a Windows host, NTFS filesystem corruption events logged in System Event Log on host end.
2023-10-12 19:35:20,Warning,2,136,NTFS,host.domain.com,The default transaction resource manager on volume encountered an error while starting and its metadata was reset.  The data contains the error code.
  • Windows fixed the filesystem in a fraction of a second as seen in message below.
2023-10-12 19:35:20,Warning,0,130,Ntfs,host.hbctxdom.com,The file system structure on volume [file://%3f/Volume%7bxxxx19-6xx5-4vx7-bxx2-cxxxxx0ec%7d]\\?\Volume{4cxzxzx9-6zz5-4zx7-bzx2-czxzxzxzxzc} has now been repaired.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.