Your best friend for file transfer.Fetch
fetch thinks that it xfers files, but they are not (5 posts)
- Started 8 years ago by chlowden
- Latest reply 8 years ago from chlowden
I am struggling to understand why when I finish uploading large files (3gigs)via fetch 5.1.1, leopard 10.5.3, fetch indicates that the files are complete, but when i open them, they are clearly missing elements.When I choose resume upload in the put menu, fetch realises that the file is not complete and files in the gaps. Is anyone else having this problem? is there a solution?
Scott McGuire Administrator
That sounds very odd; it is not a problem we've had reported to us before.
The first thing I would suggest is updating to Fetch 5.3 (which is a free update for anyone who has a Fetch 5 license) and see if that fixes the problem. If it doesn't, let us know and we'll investigate further.
I am now 5.3 and it continues. It is particularly a nuisance in the mirror mode. The basic idea for me is to emulate an rsync using the mirror function. (I strongly suggest that you offer a similar function to rsync that has an automatic checksum utility in an upcoming version. Having a checksum script for all file exchanges seems an excellent idea that is easy to impliment.) Currently, the files are first checked by date and size, but the size is defined as soon the the xfer starts, so I presume the receiving machine always believes that the file is complete even if the contents is being sent. The receiver cannot know when the file is complete without checking the contents, so I presume that there are chunks of info that can ... disappear. I am sending mpeg videos, therefore the file will play correctly until it meets a chunk of images that have not been sent, which means that I have to check by hand all the files to see if they are really intact. P2P apps, particularly Azureus, have lots of little utilities that are well adapted to large file xfer & resolving such problems of incomplete files. It would be great if this sort of thinking could be integrated into fetch.
Scott McGuire Administrator
Just for clarification - Fetch does not upload files in random chunks like a P2P app. Fetch uploads files linearly from beginning to end; so when a file is incompletely uploaded, it should be complete from the beginning to a certain point in the file; and then when you use resume upload, it uploads from that certain point to the end of the file. I realize the file doesn't work, either way, but just to give you a better idea of how Fetch works.
Having checksums for the mirror function is something we would like to implement in the future. Nevertheless, an FTP server (or Fetch) should never tell you that the upload of a file is successful if the whole file has not been uploaded.
Could you please do the following to help us analyze the problem?
* Quit Fetch, if it's running.
* Open Fetch again.
* Connect to your server.
* Try uploading one of the files that causes the problem.
* Go to the Window menu, and choose Fetch Transcript.
* Copy the entire contents of the transcript window, and paste them into a reply to this message.
We'll take a look and see if we can figure out what might be going on.
Thanks for the clarification. Will do next upload.
- Page 1