Story #6821

Updated by pulpbot over 2 years ago


 **Ticket moved to GitHub**: "pulp/pulpcore/1899": 


 It would be nice, if the sync mechanism, after reading the metadata could anticipate the (possibly) needed diskspace, compare that to the available and take appropriate action before starting to download the content units. 

 Another option might be to add a "fake_sync" or "dry_run_sync" that reports, whether disk space is sufficient. 

 It is clearly non trivial to anticipate the actual size a sync will require due to existing duplicate artifacts. 
 Nevertheless, it is not an unreasonable user expectation to have some feature like this. 
 Downloading three quarters of some large repo only to fail with zero remaining disk space is no fun. 

 Intended to resurrect this pulp2 issue for pulp3: