Skip to main content
NetApp Knowledge Base

md5sum mismatch for NFSv4.x clients using NFSv4.x Trunking

  1. Last updated
  2. Save as PDF
Views:
403
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • NFSv4.x
  • NFSv4.x client that uses Trunking
  • Cohesity Backup Application

Issue

  • When using the NFSv4.1 Trunking feature, the client experiences I/O errors and files may not be written correctly
  • While doing recovery/restore from Cohesity backup application using NFSv4.1, noticed data curruption as md5sum is different for files after restore
  • MD5sum of file before backup:

root@server /mnt/nfsv4.1]# md5sum filename
2672eb7b5f4dee9159f3519e4434bc43  filename
 

  • MD5sum of same file after backup and restore to different Ontap path:

root@server /mnt/nfsv4.1/restore_path] md5sum filename
2672eb7b5f4dee9159f3519e4436sg74  filename

  • Issue is impacting files which are large in size(<=1GB)

 

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.