search for: vna

On 11/06/2017 10:01 AM, WK wrote: > You replaced vna with vnd but it is probably not fully healed yet cuz > you had 3.8T worth of chunks to copy. No, the heal had completed. Finished about 9 hours before I rebooted. > > So you had two good nodes (vnb and vng) working and you rebooted one > of them? Three good nodes - vnb, vng, vnh...

Since my node died on friday I have a dead peer (vna) that needs to be removed. I had major issues this morning that I haven't resolve yet with all VM's going offline when I rebooted a node which I *hope * was due to quorum issues as I now have four peers in the cluster, one dead, three live. Confidence level is not high. -- Lindsa...

On 6/10/2017 4:38 PM, Lindsay Mathieson wrote: > Since my node died on friday I have a dead peer (vna) that needs to be > removed. > > > I had major issues this morning that I haven't resolve yet with all > VM's going offline when I rebooted a node which I *hope * was due to > quorum issues as I now have four peers in the cluster, one dead, three > live. > >...

On 11/06/2017 10:46 AM, WK wrote: > I thought you had removed vna as defective and then ADDED in vnh as > the replacement? > > Why is vna still there? Because I *can't* remove it. It died, was unable to be brought up. The gluster peer detach command only works with live servers - A severe problem IMHO. -- Lindsay Mathieson

I''ve implemented code to send out bogus gratuitous ARP packet from vna in order to fix CR 6701114. The webrev is at: http://jurassic.eng/net/consulte.prc/export/build/xvm-6701114/webrev Some backgroud information (see CR 6701114 for more detail): During live migration of an xVM domain from one dom0 to another, the VNIC will be moved from one switch port to another....

On 6/10/2017 5:12 PM, Lindsay Mathieson wrote: >> > > Three good nodes - vnb, vng, vnh and one dead - vna > > from node vng: > > root at vng:~# gluster peer status > Number of Peers: 3 > > Hostname: vna.proxmox.softlog > Uuid: de673495-8cb2-4328-ba00-0419357c03d7 > State: Peer in Cluster (Disconnected) > > Hostname: vnb.proxmox.softlog > Uuid: 43a1bf8c-3e69-4581-8e16...

On Sun, 11 Jun 2017 at 06:25, Lindsay Mathieson <lindsay.mathieson at gmail.com> wrote: > On 11/06/2017 10:46 AM, WK wrote: > > I thought you had removed vna as defective and then ADDED in vnh as > > the replacement? > > > > Why is vna still there? > > Because I *can't* remove it. It died, was unable to be brought up. The > gluster peer detach command only works with live servers - A severe > problem IMHO. If the dead...

...rver in which case I won't try anything fancy with trying reuse the existing data on the failed node disks, I'd rather let it resync the 3.2TB over the weekend. In which case what is the best way to replace the old failed node? the new node would have a new hostname and ip. Failed node is vna. Lets call the new node vnd I'm thinking the following: gluster volume remove-brick datastore4 replica 2 vna.proxmox.softlog:/tank/vmdata/datastore4 force gluster volume add-brick datastore4 replica 3 vnd.proxmox.softlog:/tank/vmdata/datastore4 Would that be all that is required? Existing...

On Fri, Jun 9, 2017 at 12:41 PM, <lemonnierk at ulrar.net> wrote: > > I'm thinking the following: > > > > gluster volume remove-brick datastore4 replica 2 > > vna.proxmox.softlog:/tank/vmdata/datastore4 force > > > > gluster volume add-brick datastore4 replica 3 > > vnd.proxmox.softlog:/tank/vmdata/datastore4 > > I think that should work perfectly fine yes, either that > or directly use replace-brick ? > Yes, this should be rep...

> I'm thinking the following: > > gluster volume remove-brick datastore4 replica 2 > vna.proxmox.softlog:/tank/vmdata/datastore4 force > > gluster volume add-brick datastore4 replica 3 > vnd.proxmox.softlog:/tank/vmdata/datastore4 I think that should work perfectly fine yes, either that or directly use replace-brick ? -------------- next part -------------- A non-text attach...

On 9/06/2017 9:56 PM, Pranith Kumar Karampuri wrote: > > > gluster volume remove-brick datastore4 replica 2 > > vna.proxmox.softlog:/tank/vmdata/datastore4 force > > > > gluster volume add-brick datastore4 replica 3 > > vnd.proxmox.softlog:/tank/vmdata/datastore4 > > I think that should work perfectly fine yes, either that > or directly use replace-brick ? > >...

...lib/glusterd from other nodes Is that just the file entry in "/var/lib/glusterd/peers" ? e.g I have: gluster peer status Number of Peers: 3 Hostname: vnh.proxmox.softlog Uuid: 9eb54c33-7f79-4a75-bc2b-67111bf3eae7 State: Peer in Cluster (Connected) *Hostname: vna.proxmox.softlog** **Uuid: de673495-8cb2-4328-ba00-0419357c03d7** **State: Peer in Cluster (Disconnected)** * Hostname: vnb.proxmox.softlog Uuid: 43a1bf8c-3e69-4581-8e16-f2e1462cfc36 State: Peer in Cluster (Connected) Do I just: rm /var/lib/glusterd/peers/de673495-8cb2-...

On Sun, Jun 11, 2017 at 2:12 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > > On Sun, 11 Jun 2017 at 06:25, Lindsay Mathieson < > lindsay.mathieson at gmail.com> wrote: > >> On 11/06/2017 10:46 AM, WK wrote: >> > I thought you had removed vna as defective and then ADDED in vnh as >> > the replacement? >> > >> > Why is vna still there? >> >> Because I *can't* remove it. It died, was unable to be brought up. The >> gluster peer detach command only works with live servers - A severe >>...

After googling around and reading the material on the opensolaris.org xvm community site, I still do not understanding the configuration of networking and would appreciate some assistance. Problem: I have successfully installed an hvm domU running Windows XP on opensolaris 2005.11 (build 94), and when the laptop (lenovo t61, core2 9300) is connected via the e1000g0 interface networking works

...mtu: 1500 device: e1000g0 e1000g1 type: non-vlan mtu: 1500 device: e1000g1 e1000g2 type: non-vlan mtu: 1500 device: e1000g2 e1000g3 type: non-vlan mtu: 1500 device: e1000g3 vnic900 type: non-vlan mtu: 1500 device: vnic900 # /usr/lib/vna 900 e1000g0 0:16:3e:35:68:ca #xm network-list solarisHVM Idx BE MAC Addr. handle state evt-ch tx-/rx-ring-ref BE-path 0 0 ?? 0 1 -1 -1 /-1 /local/domain/0/backend/vif/4/0 form #vrish dumpxml solarisHVM <devices> <emulator>/usr/l...

On 11/06/2017 9:38 AM, Lindsay Mathieson wrote: > Since my node died on friday I have a dead peer (vna) that needs to be > removed. > > > I had major issues this morning that I haven't resolve yet with all > VM's going offline when I rebooted a node which I *hope * was due to > quorum issues as I now have four peers in the cluster, one dead, three > live. > > &...

...Is that just the file entry in "/var/lib/glusterd/peers" ? > > > e.g I have: > > gluster peer status > Number of Peers: 3 > > Hostname: vnh.proxmox.softlog > Uuid: 9eb54c33-7f79-4a75-bc2b-67111bf3eae7 > State: Peer in Cluster (Connected) > > *Hostname: vna.proxmox.softlog* > *Uuid: de673495-8cb2-4328-ba00-0419357c03d7* > *State: Peer in Cluster (Disconnected)* > > Hostname: vnb.proxmox.softlog > Uuid: 43a1bf8c-3e69-4581-8e16-f2e1462cfc36 > State: Peer in Cluster (Connected) > > Do I just: > > rm /var/lib/glusterd/peers/d...

...src/cmd/stat/fsstat/fsstat.c usr/src/cmd/stmfadm/stmfadm.c usr/src/cmd/su/su.c usr/src/cmd/svc/milestone/net-physical usr/src/cmd/svc/milestone/network-physical.xml usr/src/cmd/svc/profile/generic_limited_net.xml usr/src/cmd/svc/profile/generic_open.xml usr/src/cmd/truss/codes.c usr/src/cmd/vna/Makefile usr/src/cmd/vna/vna.c usr/src/cmd/zfs/zfs_main.c usr/src/grub/capability usr/src/grub/grub-0.97/stage2/builtins.c usr/src/grub/grub-0.97/stage2/graphics.c usr/src/grub/grub-0.97/stage2/term.h usr/src/lib/Makefile usr/src/lib/fm/libfmd_snmp/Makefile.com usr/src/lib/libdladm/Makefil...

Hi All, I have a machine with three network cards, and the third card(named e1000g2) is in use now. I want to use e1000g2 as default NIC when I create Guest. How can I change the default NIC? I can override the default value of config/default-nic property of svc:/system/xvm/xend. But xend still use e1000g0 when creating Guest. BTW, I can explicitly set "bridge=e1000g2" when creating