Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

NetApp XCP sync error utf8 codec can't decode byte

Views:
310
Visibility:
Public
Votes:
0
Category:
netapp-xcp
Specialty:
nfs
Last Updated:

Applies to

  • NetApp XCP
  • NFS

Issue

  • During xcp sync the operation may fail with a unicode decode error shortly after a stale file handle error at the end of xcp.log:
    • nfs3 error 70: stale filehandle
    • ERROR: 'utf8' codec can't decode byte 0xc1 in position 35: invalid start byte
  • This unicode decode failure occurred due to a read trailer index error:
    • xcp read trailer index lab.repro.netapp:/repro_c_xcp/catalog/indexes/TST_srepro_c_lab/sync/sync.index read trailer
    • ERROR: 'utf8' codec can't decode byte 0xd7 in position 160: invalid continuation byte
  • Further sync attempts continue to fail with the same error.

 

Scan to view the article on your device