Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
NetApp Knowledge Base

NetApp XCP sync error utf8 codec can't decode byte

Views:
285
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.