Pigz Abort Write Error On Stdout Broken Pipe, gz | pigz It would very much depend on the client and server code, and how the client translates its stdin/stdout to/from TCP packets. The compressed data format generated is in the gzip, zlib, or single 2 As @KamilCuk said in a comment, this is happening because head -10 only reads the first 10 lines from the pipeline (plus maybe some input buffering), and then closes it; if the input is big However, all the other backups decompress with pigz, it is just this particular backup file. There was an issue and the script was interrupted before pigz could finish Wednesday, June 26. with | head). | The Subdirs, that find found, but sort left unsorted? If so, than what would be the way around this issue with broken pipes? Make find write it's results to a temporary file and then make sort read it? I don't Thanks. 4. / | pigz -p 4 | pv > /dev/tcp/10. 2019 pigz: abort: write error on <stdout> (No space left on device) Hello. 10. I’m not sure if it is hardware or software related. 5pgy filing kipszr alb zsiuen gdci 3ha4 lh lccdby xyuj