This is getting really annoying. We have scheduled maintenance right now and it keeps getting these stupid errors
INFO: status: 14% (18071158784/128849018880), sparse 0% (885256192), duration 440, 54/49 MB/s
lzop: No space left on device: <stdout>
INFO: status: 14% (18214944768/128849018880)...
The disk couldnt move and then it corrupted the lv ... i had to restore from a 24 hour backup - customer is not happy ... this should be looked into guys
TASK ERROR: storage migration failed: mirroring error: error job is not mirroring at /usr/share/perl5/PVE/QemuServer.pm line 4691.
I got that - and if I change disk to vm-100-disk-2 it works
http://pve.proxmox.com/wiki/Network_Model
Why would you need to do vlans this way? Let's say I have 4 nodes each with 2 nics
Node 1: NIC A and NIC B
Node 2: NIC C and NIC D
Node 3: NIC E and NIC F
Node 4: NIC G and NIC H
On the switch
port 1: public network drop
port 2, 3, 4, 5 have NICs A...
I have a VM ID 100
Disk 1 on SAN is VM-100-Disk-1.
Disk 2 on NFS is VM-100-Disk-1
when you mvoe the name overlaps. Shouldn't that second disk be VM-100-Disk-1 when you move or when it's just sitting there?
Node to VM - I get about 30 mbps
Node to Node - I get about 200mbps
Node to external server - I get about 50 mbps
VM to external server - I get 1 mbps ...
Not all clients are using LVM so need a stable solution.
I did it using resize2fs - I was doing it on partition 1 which is obviously at the full length. Needed to do it for the full disk. I eraesd and recreated the partition and did resize2fs and an fsck
not so elegant but it worked
Did that - it doesn't work. Internet is not an issue since I have VMBR0 as the public VLAN and VMBR1 and VMBR2 as eth1 and eth2
VMBR3 and VMBR4 are both bound to eth3 with the ips 10.10.3.x and 10.10.4.x
The 10.10.3.x works but not 4.x ... I presume you can't bind 2 diff subnets to the same...
Hi guys,
I know for each individual NIC its tough to have different IP ranges with diffferent gateways. However, how do I bind multiple private vLANs to 1 nic ie 10.10.1.x and 10.10.2.x
I bound it manually through vmbr1:1 and vmbr1:2 - but is there a more elegant way of doing this?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.