Partial-File Safety

A file is not a fact until it is finished — but nothing about a filename says whether the bytes behind it are all there. The consumer that reads a file mid-write gets a truncated CSV, a corrupt archive, or a half-record that poisons a database load. The failure looks like anything except what it was. Partial-file reads are among the most common and least diagnosed failures in automated file exchange.

This series closes the gap. It explains why partial reads happen and the producer-side fixes - temp names, atomic renames, marker files. It covers the consumer-side defenses when you do not control the producer, and what happens when the transfer itself dies midway. It provides a checklist for auditing any flow's exposure. This is the deep companion to our watch-folder series, which covers the workflow surrounding these mechanics.

Articles in This Series

• Why Consumers Read Half-Written Files
  See the race condition on a timeline: writer starts, watcher fires, reader loses. Learn where it bites hardest, what the failures look like downstream, and why it evades diagnosis for months.
• Temp Names and Atomic Renames: The Core Fix
  Write to a temporary name, rename when done. This article covers why rename is the atomic moment, the same-filesystem caveat, in-flight naming conventions, and platform notes told honestly.
• Marker and Control Files: Signaling Done
  The done-file pattern: ready markers, trigger files, ordering guarantees, cleanup discipline, when markers beat renames - and the orphan-marker pitfalls to design against.
• Size-Stability and Settle Checks: The Consumer's Defense
  When the producer will not cooperate: stable-size polling, minimum-age rules, the honest limits of open-handle checks, and tuning settle intervals for real sender behavior.
• When the Transfer Itself Dies Midway
  This article covers the network side of partial files: receiving into temp names, and what resume can and cannot promise. It covers verifying completeness with sizes and hashes, and server-side upload behaviors worth knowing.
• The Partial-File Safety Checklist for Any Flow
  See producer, consumer, and both-sides controls in one matrix. This article covers auditing an existing flow and ranking retrofits by effort. It includes a worked audit of one risky flow made safe.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. It pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.