The BitTorrent crash scenario doesn't indicate a bug. The only way for an application to know about uncommitted writes is to scan the file (for example by rehashing in this instance). To avoid doing this every time it's started, it saves a record of what parts have been downloaded. In a crash, this record may be more up to date than what's actually saved to the disk.
The BitTorrent crash scenario doesn't indicate a bug. The only way for an application to know about uncommitted writes is to scan the file (for example by rehashing in this instance). To avoid doing this every time it's started, it saves a record of what parts have been downloaded. In a crash, this record may be more up to date than what's actually saved to the disk.