cannot git clone to mounted dir

[marosg42]

Cloning into mounted dir fails (tried also other repos, same result)

~/git$ git clone https://github.com/CanonicalLtd/multipass.git
Cloning into 'multipass'...
remote: Counting objects: 664, done.
remote: Compressing objects: 100% (20/20), done.
remote: Total 664 (delta 9), reused 16 (delta 6), pack-reused 637
Receiving objects: 100% (664/664), 263.22 KiB | 95.00 KiB/s, done.
fatal: premature end of pack file, 68 bytes missing
fatal: index-pack failed

Works ok inside VM outside mounted dir

~$ git clone https://github.com/CanonicalLtd/multipass.git
Cloning into 'multipass'...
remote: Counting objects: 664, done.
remote: Compressing objects: 100% (20/20), done.
remote: Total 664 (delta 9), reused 16 (delta 6), pack-reused 637
Receiving objects: 100% (664/664), 263.22 KiB | 421.00 KiB/s, done.
Resolving deltas: 100% (399/399), done.

latest edge version

tracking:               edge
installed:              2017.2.3-15-g3b0f808 (124) 63MB classic
refreshed:              2018-01-30 17:00:20 +0100 CET
channels:                                          
  stable:               –                               
  candidate:            –                               
  beta:                 2017.2.3             (111) 63MB classic
  edge:                 2017.2.3-15-g3b0f808 (124) 63MB classic

[townsend2010]

This is strange...I can reproduce this issue 100% of the time. However, if I revert #80, the issue still remains. I did not see this when developing #80, so I'm stumped as to what is going on now...

[townsend2010]

An interesting data point is that particular issue occurs when setting the --cpu option on launch to 2 or greater. git uses multiple threads to read the pack file if 2 or more cpu's are present. So this to me either indicates a race or somehow client messages are being received out of order.

[marosg42]

Interesting find. Yes, my VM is set with multiple CPUs

…

On Wed, Jan 31, 2018 at 7:59 PM, Chris Townsend ***@***.***> wrote: An interesting data point is that particular issue occurs when setting the --cpu option on launch to 2 or greater. git uses multiple threads to read the pack file if 2 or more cpu's are present. So this to me either indicates a race or somehow client messages are being received out of order. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#83 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APx7QnVyFXY0kzUtmB0OJvgzu5hkuZgiks5tQLgEgaJpZM4Ryyoi> .

-- "The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind."