You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case when space is not enough on the server side the stream.write operation fails with ConnectionResetError.
msg is like that 'Connection lost', and that's it, nothing is useful at all:
Is there way to recognize that the problem is related to the shortage of volume rather than network issue?
If there is, then it would be helpful to make a stop of uploading instead of keep trying to reconnect endlessly.
Here is an example which shows something similar i suppose to have:
Yes, it is possible, but should be implemented in 3 places:
PathIO level
Server level
Client level
There are some return codes, which represents such cases:
452 Requested action not taken.
Insufficient storage space in system.
552 Requested file action aborted.
Exceeded storage allocation (for current directory or
dataset).
I've tried to check server response for popular ftp servers, which run from docker.
garethflowers/ftp-server
delfer/alpine-ftp-server
Both have broken pipeline without any excuse. I had only this:
BrokenPipeError(32, 'Broken pipe')
Nothing about error with codes 552 or 452. (upd.)
Also i found that the final exception will differ from time to time. I use 100Mb partition for ftp volume, and vary initial files' set and chunk size before start.
File "/home/user/.local/share/python3.10/lib/python3.10/asyncio/streams.py", line 167, in _drain_helper raise ConnectionResetError('Connection lost')
File "/home/user/.local/share/python3.10/lib/python3.10/asyncio/selector_events.py", line 949, in _write_ready n = self._sock.send(self._buffer) BrokenPipeError: [Errno 32] Broken pipe
Could someone specify which impl of ftp server is full enough to handle disk full (452, 552 error codes) carefully?
updated: i found the way to adjust an ftp server to send me a response of 552 error code.
In case when space is not enough on the server side the stream.write operation fails with ConnectionResetError.
msg is like that 'Connection lost', and that's it, nothing is useful at all:
Is there way to recognize that the problem is related to the shortage of volume rather than network issue?
If there is, then it would be helpful to make a stop of uploading instead of keep trying to reconnect endlessly.
Here is an example which shows something similar i suppose to have:
The text was updated successfully, but these errors were encountered: