Tar/Gzip processes never ending for WinSCP

Advertisement

Inuya5ha
Joined:
Posts:
4
Location:
Argentina

Tar/Gzip processes never ending for WinSCP

Program: WinSCP 4.3.5.1463 (and older)
OS: Windows XP SP3 (ES)
Protocol: SCP

Hi, I'm using WinSCP to compress directories with several thousand of small files on them. Resulting TAR or TGZ files may be 10 to 60 GB in size, this process can take more than 8 hours even in the fastest servers.

After using the built-in Tar/Gzip custom command (or a modified command to prevent Gzip compression and just make uncompressed TAR), if the operation took too long, WinSCP will never remove the dialog "Host is not communicating for more than 15 seconds. Still waiting..." with the Abort and Help buttons.

So in order to create these TAR files (for server migration, in this case) I must constantly monitor the file size via FTP with another client, and manually check when the file size stops growing. This is certainly annoying.

WinSCP might be waiting for a reply that probably never arrives, or the program hangs when the reply arrived because of the extremely long delay, and this happens with any server and not just this. I previously had this issue in all my older servers.

It would be great to provide a handler for TAR and GZIP operations, that manually checks the file size every few seconds, and show it to the user. This will also cause the program to be aware of the end of the process instead of showing the Abort dialog forever.

I hope everything is clear, sorry for my english but my native language is spanish.

Reply with quote

Advertisement

xbliss
Joined:
Posts:
1

Had this TAR issue today as well. Has this been resolved or fixed in a release/ version?

Had this TAR issue today as well. Has this been resolved or fixed in a release/ version?

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
41,442
Location:
Prague, Czechia

Re: Had this TAR issue today as well. Has this been resolved or fixed in a release/ version?

xbliss wrote:

Had this TAR issue today as well. Has this been resolved or fixed in a release/ version?
Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

Advertisement

You can post new topics in this forum