Cm fast export creating faulty dumps

Unity Services
,
1

I am currently migrating to git, but non of the methods of plasticscm seem to work. Under ubuntu the tool wouldn’t sync to the a git repo in the first place:

cm sync epo@owner@cloud git git@server:owner/repo.git
- 0 changesets to pull
- 468 changesets to push

Receiving references... OK
There are changes to push.
Error: No space left on device : '/tmp/efc6675b-a30f-423b-8e94-09e201fb0f57/.git/objects/2c/0df534267603db6f57dc9c112760ed5afc9445

I then tried to use fast export:

cm fast-export repo@owner@cloud ../pastic.dump
...
cat ../plastic.dump | git fast-import
fatal: Path Assets/some/path/here not in branch                                                                            
fast-import: dumping crash report to .git/fast_import_crash_11804

How is it that nothing of this works?

2

Hi, it seems that the gitsync operation is using “/tmp” to build the replication package but your machine is getting out of free disk on this path.

Can you try to add more disk to the system tmp path or run the “cm sync” operation from a different machine with enough disk space?

3

Hey, thanks for the suggestion, but unfortunately I cant add more disk space. I already allocated like 40G. But for a project of this size, you would need propably even more. Can it be done, that project is not dumped into memory?

4

Hi, I’m afraid that Plastic is creating a replicating package on the temporary path that needs to be sent to the git server. Note that you can run the “cm sync” command from any machine where you have Plastic installed. Not sure if you have more disk space in some other machine.

5

Hey, sorry I didnt describe the Problem precisely. Having a temporary path for storage is not an issue, but dumping 60G Project Files into my RAM is.

6

Using GitSync: The max storage used in the TMP path is linked to your bigger checkin (not related to the repository size) if you have a checkin of 10GB you may need that amount of free disk in the TMP path.

You shouldn’t need a lot of RAM to run a GitSync operation. Checking your original screenshot, the problem was “not space left on the TMP path”.

5:06

Rubén de Alba

Dudo mucho que estemos cargando todo el contenido del fichero en memoria/RAM, eso no tiene ningún sentido.

8

Sorry, I was wrong about the RAM thing. Is there a way to to not use /tmp but another path for the caching?

9

We are using the system environment variable for tmp. If you change the environment variable path, it should work also for GitSync.