Re: 2.7 pre-release: Virtual memory exploding and dar locks up

Hi

On 30.03.21 21:48, Denis Corbin wrote:
> pay attention to the fact tar uses a default compression ratio (usually
> 6 depending on the compression binary) while dar use the maximum
> available (9 or more depending on the algo used). You can tune that with
> dar (not with tar AFAIK) thanks to the -z option (see details in man page).
> 

yeah, for that reason my pipeline was actually

storage box of origin:
tar c | mbuffer --TCP-->

powerful CPU box:
mbuffer | xz -9 [...] | mbuffer --TCP-->

storage box for tarballs:
mbuffer | split --> local storage

which in principle would still work except the new requirement of quasi 
random access to few files within the end results which tar would not 
allow, hence: *dar* :)

> nothing at fault on your command, dar/libdar should tell it else, most
> probably a bug I have not yet met in the non-regression tests currently
> running...
> 
> I will try to reproduce your context and see whether I also met this
> problem so I can fix it. Thanks for feedback!

If I can assist in any way, feel free to contact me on or off-list. If 
you cannot reproduce the issue I can try to organize access to a machine 
where I see this - but that would probably mean me going to the data 
center once again and single out a machine for you (some effort but doable).

Cheers

Carsten
-- 
Dr. Carsten Aulbert, Max Planck Institute for Gravitational Physics,
Callinstraße 38, 30167 Hannover, Germany, Phone +49 511 762 17185

_______________________________________________
Dar-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dar-support