jspcc
Trekkie
 Offline
Posts: 15
|
 |
« on: July 10, 2010, 08:39:37 AM » |
|
Download the file to be not only wrong, and the MD5 is different! . Thank you
|
|
|
|
|
Logged
|
|
|
|
|
SilviuB
|
|
« Reply #1 on: July 10, 2010, 12:37:04 PM » |
|
i have the same problem ... they said that my internet connection was the problem.
|
|
|
|
|
Logged
|
|
|
|
|
MrPhil
|
|
« Reply #2 on: July 10, 2010, 12:41:17 PM » |
|
So you have a "backup file" on your server, that you want to download to your PC? First of all, what kind of backup? A "tar" or "tgz" file will need to be downloaded in binary format to avoid corruption. On the other hand, a database "sql" file is ordinary text and can be downloaded in ASCII/text format (if you want to work with it on your PC) or binary if you're only going to store it there.
What are you using to FTP the backup? Are you letting it "auto" choose the mode, or are you forcing the (wrong) mode?
|
|
|
|
|
Logged
|
|
|
|
jspcc
Trekkie
Offline
Posts: 15
|
|
« Reply #3 on: July 10, 2010, 08:12:17 PM » |
|
Hello
I use the full backup;
A whole "tar.gz" packages;
Download transmission using two binary mode;
Model used in automatic mode;
Software "FileZilla-3.3.3"
Thanks
|
|
|
|
|
Logged
|
|
|
|
|
SilviuB
|
|
« Reply #4 on: July 10, 2010, 10:33:38 PM » |
|
Hello
I use the full backup;
A whole "tar.gz" packages;
Download transmission using two binary mode;
Model used in automatic mode;
Software "FileZilla-3.3.3"
Thanks
Same for me. |
|
|
|
|
Logged
|
|
|
|
|
MrPhil
|
|
« Reply #5 on: July 11, 2010, 08:58:16 AM » |
|
If the file you're downloading is "tar.gz", you need to make sure it's transferred in binary mode. I'm not sure what "two binary mode" is. It should be the same size (byte count) and have the same MD5 checksum on your PC as it does on the server. FileZilla should know how to select binary mode automatically -- you're not manually overriding its choice, are you? If you're not sure if FZ is making the right choice, select "binary" if given the chance. When you get the file on to your PC, do a DIR and see if it's exactly the same size. If it is, but the MD5 is different, could it be you're using (or misusing) a wrong (or bad) MD5 module on either end? You're not editing the file after downloading it, are you? That will definitely corrupt it (even to just look inside it, if you make the mistake of saving the file instead of quitting the editor). The acid test would be to upload the backup to the server (under a different name) and compare the two files and see if they're different.
If that doesn't solve it, you'll need to work with LP support to see what's going on.
|
|
|
|
|
Logged
|
|
|
|
|
SilviuB
|
|
« Reply #6 on: July 11, 2010, 09:26:47 AM » |
|
The archive is the same size ( to the last byte ), but the MD5 is different. I used FileZilla, CuteFTP and SmartFTP but nothing is working. All i do is just download and then try to extract the content ( winzip, winrar and 7-zip ) ... but i get the same error. The files that is causing the error is the home.tar.gz. I tried using 5 MD5 programs ... same result.
I told the LP support and the archive is valid on the server, but it gets corrupted during the download process.
My archive size is 4.5 - 5 GB and the problems started after 25 June 2010. jspcc when did you started having problems?
|
|
|
|
|
Logged
|
|
|
|
jspcc
Trekkie
Offline
Posts: 15
|
|
« Reply #7 on: July 11, 2010, 03:17:18 PM » |
|
I confirm that I am using the "FZ" download, which is the binary model; File size, like the last one; MD5 is different, not normal extract; File Size 6GB; Download location is "https: / / secure.daybreak.lunarbreeze.com", download from here, as the host of shared IP has been closed. Probably date should also be in June, from the beginning I have downloaded a lot of times the backup experiment. At the same time thank you "MrPhil" answers.  |
|
|
|
|
Logged
|
|
|
|
|
SilviuB
|
|
« Reply #8 on: July 11, 2010, 09:05:31 PM » |
|
I'm on the sapphire server ... so 2 servers with the same problem.
|
|
|
|
|
Logged
|
|
|
|
|
MrPhil
|
|
« Reply #9 on: July 12, 2010, 02:48:04 PM » |
|
A 4.5 to 6 GB file is a bit on the large side -- it might exceed some internal limit (2 or 4GB?) in FTP. The correct number of bytes came down, so it doesn't sound like the job timed out. You might mention the file size to LP if you haven't already. Just for fun, you might try downloading something just under 4.2GB, and if that fails, just under 2.1GB. If one of them works, you may have found a code limit (32 bit signed or unsigned integer). LP might be able to suggest a client that will work with larger files, or they might know that their end can't exceed some certain amount. One workaround might be to use the "dd" or "split" command ( http://www.techiecorner.com/107/how-to-split-large-file-into-several-smaller-files-linux/) to break up large files into smaller chunks, and download them separately. They can be reassembled on either Linux or Windows on the PC end, although you may want to keep them separate, in case you need to upload them again to restore. |
|
|
|
|
Logged
|
|
|
|
|
Nika
Guest
|
|
« Reply #10 on: July 13, 2010, 07:52:03 AM » |
|
I have not seen another report of this. You may want to send in a support ticket and advise that this only occurs after you have fully downloaded and tried to extract the backup.
|
|
|
|
|
Logged
|
|
|
|
|
SilviuB
|
|
« Reply #11 on: July 13, 2010, 07:58:01 AM » |
|
@Nika: i did that before this thread was started ... and the result was that my internet connection is bad ... now that i see another user with the same problem i don't think that the main problem is my internet connection.
|
|
|
|
|
Logged
|
|
|
|
|
MrPhil
|
|
« Reply #12 on: July 13, 2010, 10:42:48 AM » |
|
Googling FTP client size limit, I found some entries suggesting that FTP is limited to as little as 2GB (possibly 4GB). One source said he'd never been able to transfer more than 4GB on any server or client, while another said he could transfer 150GB on Linux. Another thing to note is that Windows "FAT" filesystems have limits under 4GB, so it's possible that the file corruption occurred on your local machine. Finally, I'm sure that FTP has to keep count of bytes going through somewhere, and 32 bit integers are still the norm, so 2GB or 4GB limits would not be unexpected.
|
|
|
|
|
Logged
|
|
|
|
jspcc
Trekkie
Offline
Posts: 15
|
|
« Reply #13 on: July 14, 2010, 06:03:57 AM » |
|
"LP" is requesting "CPANEL" repair personnel.
|
|
|
|
|
Logged
|
|
|
|
|
MrPhil
|
|
« Reply #14 on: July 14, 2010, 08:24:24 AM » |
|
If LP support seems to be stumped, be sure to point them to my comments in this topic re: 2GB or 4GB limit. They may not be aware of it off the top of their heads (if it is, in fact, the key to the problem). If it is the problem, it's probably nothing that the cPanel folks will be able to fix (it's the FTP server).
If there is such a limit, all I can suggest is running "split" (via SSH or a cron job) to split up the offending file into 1GB or smaller chunks, downloading them, and reassembling the file on your PC (if you need to use it on your PC, and provided you're using NTFS if on Windows). You might want to try it anyway, just to see if downloading in 1GB chunks does the job (which would suggest that there is a 2GB or 4GB limit). You can always re-upload the chunks and reassemble on the server, and compare against the original, to make sure they're identical (diff command).
|
|
|
|
|
Logged
|
|
|
|
|
