In article <[email protected]>, RVP <[email protected]> wrote: >On Tue, 29 Jun 2021, Louis Guillaume wrote: > >>>> ./usr/share/locale/zh_CN.GB18030 >>>> ./usr/share/locale/zh_CN.GB18030/LC_CTYPEgzip: Unexpected end of input >>>> >>>> pax: End of archive volume 1 reached >>>> pax: ustar vol 1, 4942 files, 189618300 bytes read, 0 bytes written in 36 >>>> secs (5267175 bytes/sec) >>>> >>>> ATTENTION! pax archive volume change required. >>>> Ready for archive volume: 2 >>>> Input archive name or "." to quit pax. >>>> 98% |***************************************************** | 40544 KiB >>>> 750.71 KiB/s - stalled -^C >>>> pax: Signal caught, cleaning up. >>>> >>>> >>>> As if the pipe to pax is misbehaving. > >I get: > >ftp: Writing `|pax -zrvpe': Interrupted system call >gzip: Unexpected end of input > >pax: End of archive volume 1 reached >pax: ustar vol 1, 2927 files, 169593513 bytes read, 0 bytes written in >72 secs (2355465 bytes/sec) > >This seems to be caused by the write to the pax pipe being interrupted >by the alarm signal used to print the progress bar. The code should >retry in such cases. > >You should file a PR for this. In the mean time, the work-around >is to disable the ftp progress-bar using -V (you already have `pax >-v ...').
Can you ktrace to find what system call gets interrupted? Thanks, christos
