Rclone will store the source timestamp in a custom object metadata field called orig-mtime .
To understand the error, we must first understand the cargo. When we talk about a file, we usually think of the content—the text in the document, the pixels in the photo, or the audio in the song. This is the "data."
Few error messages are as cryptic—and as frustrating—as If you are reading this, you have likely just watched a file copy operation fail, a backup job abort, or a virtual machine migration grind to a halt. You are not alone. metadata xfer not supported
The error (Metadata Transfer Not Supported) is a status message frequently encountered in BitTorrent clients—most notably Tixati —indicating that a connected peer is unable or unwilling to share the essential "blueprint" of a file. While it is most common in P2P file sharing, similar metadata failures also occur in enterprise storage systems like NetApp and Dell EMC due to permission or connectivity issues. 1. Understanding the Error in BitTorrent
When the destination a piece of metadata, the SDK/CLI aborts rather than silently drop it, because data‑governance policies often require explicit handling. Rclone will store the source timestamp in a
Add the --no-perms (ignore permission preservation) and --no-xattrs flags:
# Re‑upload with metadata gsutil cp gs://src-bucket/file.txt - | \ gsutil -h "x-goog-meta-$CUSTOM" cp - gs://dest-bucket/file.txt This is the "data
kubectl exec source-pod -- tar cf - /data | kubectl exec dest-pod -- tar xvf - -C /