On 2019-08-01, Rudolf Sykora <rsyk...@disroot.org> wrote: > (The problem stays with scp, or anything, once a network device > (localhost is enough) participates.)
(For your tar | nc, you'll need nc -N or nc -w1 or something to shutdown the connection after the end of file, though this is beside the point if other methods are failing too). What happens if you "tcpbench -s" in one terminal, and "tcpbench localhost" in another? (i.e. is the problem just with network access, or does it only happen when also reading and/or writing files?) > Nobody spoke about "deliberately", or working in a "binary" way. > In the follow-up I added the information that the size of files can be > larger than 10 GB. In some systems (e.g. plan9) there are quite a few > limits/constants which lead, or can lead, to problems when > exceeded. That is what was meant by the settings. Should be no issues with FFS or NFSv3. NFSv2 and FAT do have smaller limits. I think others will have trouble figuring out what's going on unless you can determine what's unusual about your system that is causing this ..
