メインコンテンツまでスキップ

CONTAP-348855:特定のNetAppプラットフォームのLUNまたはNVMeネームスペースでSAN接続ホストをホストすると、チェックサムの読み取り検証エラーが断続的に発生することがある

Views:
5
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

問題

まれに、NVMeネームスペースにホストされているデータ、またはプラットフォームA1K、A70、A90からのNetApp FCPまたはiSCSI LUNからの特定のブロックの初回読み取り処理中に、ONTAPから誤ったユーザデータが提供されることがあります。
シグネチャの例:

  • ページインCRC違反を参照しているBSODでWindowsがクラッシュする:

Bug Check: 0x0000001a Parameter1: 0x3f
  • Oracle alertlogから次のようなシーケンスが報告されます。

Corrupt block relative dba: 0x0000c4cd (file 42, block 50381)  
Reread (file 42, block 50381) found valid data
Repaired corruption at (file 42, block 50381)  

MSSQLログで次のようなエラーが報告されます。

  • A read of the file 'D:\path\file.mdf' at offset 0x0000006d70a000 succeeded after failing 1 time(s) with error: torn page (expected signature: 0x00000000; actual signature: 0x00c03444). Additional messages in the SQL Server error log and operating system error log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

    または
    A read of the file 'C:\path_to\data.mdf' at offset 0x00000001a22000 succeeded after failing 1 time(s) with error: incorrect checksum (expected: 0x02c078e3; actual: 0x4dab258e). Additional messages in the SQL Server error log and operating system error log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

    または
    A read of the file 'D:\path_toe\system.mdf' at offset 0x0000006d70e000 succeeded after failing 1 time(s) with error: incorrect pageid (expected 1:224135; actual 27267:-1332691384). Additional messages in the SQL Server error log and operating system error log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.


その後、同じ論理ブロックアドレスへの読み取りが成功し、エラーは報告されません。
この問題は、9.15.1以上のプラットホームでのAFFとASA variantの両方に適用できます。
9.16.1RC1以降を実行しているシステムは、この問題の影響を受けません。

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.