That's very similar setup to mine. Can you also try OpenSSH
sftp client?
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- AnrDaemon
Ubuntu 12.04.
OpenSSH_5.9p1 Debian-5ubuntu1.4, OpenSSL 1.0.1 14 Mar 2012
OpenSSH_5.9p1 Debian-5ubuntu1.4, OpenSSL 1.0.1 14 Mar 2012
- martin
Re: WinSCP fail when receiving server's disk is full.
I was not able to reproduce your problem.
With SFTP, I get (as expected) an infamous "Code 4: Failure" error when the disk is full.
https://winscp.net/eng/docs/sftp_codes#code_4
With SCP is get "No space left on device".
What server are you connecting to?
With SFTP, I get (as expected) an infamous "Code 4: Failure" error when the disk is full.
https://winscp.net/eng/docs/sftp_codes#code_4
With SCP is get "No space left on device".
What server are you connecting to?
- AnrDaemon
WinSCP fail when receiving server's disk is full.
Once the disk on receiving side reach its end, WinSCP receive a packet it can't decode.
scp (tested on Cygwin SCP) correctly tells that there's "no space left on device". Though, scp will first sit there and pour entire file into void, before spelling the error.
Also, NetBox (based on WinSCP code) spell a little more verbose about the error:
Error decoding SFTP packet (9, 4, 9)
---------------------------
Error
---------------------------
Incoming packet was garbled on decryption
---------------------------
Abort Reconnect Help
---------------------------
scp (tested on Cygwin SCP) correctly tells that there's "no space left on device". Though, scp will first sit there and pour entire file into void, before spelling the error.
Also, NetBox (based on WinSCP code) spell a little more verbose about the error:
Error decoding SFTP packet (9, 4, 9)