Re: git clone failing in vmm
On Sat, Mar 04, 2017 at 01:31:31PM +1300, Carlin Bingham wrote: > I'm having an issue with git clone failing in a vmm vm. Happens consistently > for any large trees, example: > > $ git clone https://github.com/openbsd/src.git > Cloning into 'src'... > remote: Counting objects: 1672334, done. > remote: Compressing objects: 100% (867/867), done. > fatal: pack has bad object at offset 2242336: inflate returned -5 > fatal: index-pack failed > > This doesn't happen outside the vm. > > Syslog on the host says this: > Mar 4 12:12:40 vorpal vmd[99431]: vionet queue notify - no space, dropping > packet > > Other downloads (eg. downloading the sets) works fine, it's just git that > fails. > > Anyone know what the problem might be or how to prevent it? > I can reproduce this, although it's not the problem I thought it was. I'll see if I can get some time to look into this soon, but I am starting to get a bit backlogged with vmm work. -ml
Re: git clone failing in vmm
You completely missed the point. -- Ville On Mar 4, 2017 21:09, "Flipchan" <flipc...@riseup.net> wrote: U Can download the zip File for the master branch instead of useing git Carlin Bingham <c...@viennan.net> skrev: (4 mars 2017 01:31:31 CET) >I'm having an issue with git clone failing in a vmm vm. Happens >consistently >for any large trees, example: > >$ git clone https://github.com/openbsd/src.git > >Cloning into 'src'... >remote: Counting objects: 1672334, done. >remote: Compressing objects: 100% (867/867), done. >fatal: pack has bad object at offset 2242336: inflate returned -5 >fatal: index-pack failed > >This doesn't happen outside the vm. > >Syslog on the host says this: >Mar 4 12:12:40 vorpal vmd[99431]: vionet queue notify - no space, >dropping packet > >Other downloads (eg. downloading the sets) works fine, it's just git >that >fails. > >Anyone know what the problem might be or how to prevent it? > > >The network on the host looks like this: > >vether0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu >1500 >lladdr fe:e1:ba:d1:a5:21 >index 8 priority 0 llprio 3 >groups: vether >media: Ethernet autoselect >status: active >inet 10.1.1.1 netmask 0xff00 broadcast 10.1.1.255 >bridge0: flags=41<UP,RUNNING> >index 9 llprio 3 >groups: bridge > priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp >vether0 flags=3<LEARNING,DISCOVER> >port 8 ifpriority 0 ifcost 0 >tap0 flags=3<LEARNING,DISCOVER> >port 10 ifpriority 0 ifcost 0 >tap0: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 >lladdr fe:e1:ba:d2:bb:43 >description: vm2-if0-tmpvm >index 10 priority 0 llprio 3 >groups: tap >status: active > >-- >Carlin -- Sincerly flipchan - LayerProx dev
Re: git clone failing in vmm
U Can download the zip File for the master branch instead of useing git Carlin Bingham <c...@viennan.net> skrev: (4 mars 2017 01:31:31 CET) >I'm having an issue with git clone failing in a vmm vm. Happens >consistently >for any large trees, example: > >$ git clone https://github.com/openbsd/src.git > >Cloning into 'src'... >remote: Counting objects: 1672334, done. >remote: Compressing objects: 100% (867/867), done. >fatal: pack has bad object at offset 2242336: inflate returned -5 >fatal: index-pack failed > >This doesn't happen outside the vm. > >Syslog on the host says this: >Mar 4 12:12:40 vorpal vmd[99431]: vionet queue notify - no space, >dropping packet > >Other downloads (eg. downloading the sets) works fine, it's just git >that >fails. > >Anyone know what the problem might be or how to prevent it? > > >The network on the host looks like this: > >vether0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu >1500 >lladdr fe:e1:ba:d1:a5:21 >index 8 priority 0 llprio 3 >groups: vether >media: Ethernet autoselect >status: active >inet 10.1.1.1 netmask 0xff00 broadcast 10.1.1.255 >bridge0: flags=41<UP,RUNNING> >index 9 llprio 3 >groups: bridge > priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp >vether0 flags=3<LEARNING,DISCOVER> >port 8 ifpriority 0 ifcost 0 >tap0 flags=3<LEARNING,DISCOVER> >port 10 ifpriority 0 ifcost 0 >tap0: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 >lladdr fe:e1:ba:d2:bb:43 >description: vm2-if0-tmpvm >index 10 priority 0 llprio 3 >groups: tap >status: active > >-- >Carlin -- Sincerly flipchan - LayerProx dev
Re: git clone failing in vmm
On Sat, Mar 04, 2017 at 01:31:31PM +1300, Carlin Bingham wrote: > I'm having an issue with git clone failing in a vmm vm. Happens consistently > for any large trees, example: > > $ git clone https://github.com/openbsd/src.git > Cloning into 'src'... > remote: Counting objects: 1672334, done. > remote: Compressing objects: 100% (867/867), done. > fatal: pack has bad object at offset 2242336: inflate returned -5 > fatal: index-pack failed > > This doesn't happen outside the vm. > Thanks for reporting this. I have seen other similar failures. I think I know what's going on but I don't have a fix yet. I will let you know when I do. -ml > Syslog on the host says this: > Mar 4 12:12:40 vorpal vmd[99431]: vionet queue notify - no space, dropping > packet > > Other downloads (eg. downloading the sets) works fine, it's just git that > fails. > > Anyone know what the problem might be or how to prevent it? > > > The network on the host looks like this: > > vether0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > lladdr fe:e1:ba:d1:a5:21 > index 8 priority 0 llprio 3 > groups: vether > media: Ethernet autoselect > status: active > inet 10.1.1.1 netmask 0xff00 broadcast 10.1.1.255 > bridge0: flags=41<UP,RUNNING> > index 9 llprio 3 > groups: bridge > priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp > vether0 flags=3<LEARNING,DISCOVER> > port 8 ifpriority 0 ifcost 0 > tap0 flags=3<LEARNING,DISCOVER> > port 10 ifpriority 0 ifcost 0 > tap0: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > lladdr fe:e1:ba:d2:bb:43 > description: vm2-if0-tmpvm > index 10 priority 0 llprio 3 > groups: tap > status: active > > -- > Carlin
git clone failing in vmm
I'm having an issue with git clone failing in a vmm vm. Happens consistently for any large trees, example: $ git clone https://github.com/openbsd/src.git Cloning into 'src'... remote: Counting objects: 1672334, done. remote: Compressing objects: 100% (867/867), done. fatal: pack has bad object at offset 2242336: inflate returned -5 fatal: index-pack failed This doesn't happen outside the vm. Syslog on the host says this: Mar 4 12:12:40 vorpal vmd[99431]: vionet queue notify - no space, dropping packet Other downloads (eg. downloading the sets) works fine, it's just git that fails. Anyone know what the problem might be or how to prevent it? The network on the host looks like this: vether0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 lladdr fe:e1:ba:d1:a5:21 index 8 priority 0 llprio 3 groups: vether media: Ethernet autoselect status: active inet 10.1.1.1 netmask 0xff00 broadcast 10.1.1.255 bridge0: flags=41<UP,RUNNING> index 9 llprio 3 groups: bridge priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp vether0 flags=3<LEARNING,DISCOVER> port 8 ifpriority 0 ifcost 0 tap0 flags=3<LEARNING,DISCOVER> port 10 ifpriority 0 ifcost 0 tap0: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 lladdr fe:e1:ba:d2:bb:43 description: vm2-if0-tmpvm index 10 priority 0 llprio 3 groups: tap status: active -- Carlin
