Output of restic version

➜ ~ restic128mb version
restic 0.9.5 compiled with go1.11.1 on linux/amd64

What should restic do differently? Which functionality do you think we should add?

Restic has https://github.com/restic/restic/blob/master/internal/repository/packer_manager.go#L39
and https://github.com/restic/restic/blob/master/internal/restorer/filerestorer.go#L30 which specify approximate pack size which restic tries to target.

A good number of remote data storage have a limitation on the number of files, I have run into issues with Google Team Drive, and PUR based storage at work (it is full flash system, with glusterfs over the top). It should be reasonable to update the pack size on a repo level to enable varied use-cases.

What are you trying to do?

Either store the target pack size in the repo metadata or allow user to pass the parameter while backup (and maybe try to figure out the appropriate size for cache at the time of restore, for now a simple option to be given both times should work well)

Did restic help you or made you happy in any way?

Thank fully I haven;t had to restore data in an emergency, but I have tried to restore data as a disaster recovery exercise which provides comfort that restic has my back.