Displaying 3 results from an estimated 3 matches for "bbfd".
Did you mean:
bfd
2012 Nov 27
1
Performance after failover
...d succeeded went straight
to the second server,
with throughput still at ~25MB/s.
Is this the expected behavior for clients that have failed over from one
server to another ?
torbjorn at srv18:~$ sudo gluster volume$
Volume Name: testvol$
Type: Distributed-Replicate$
Volume ID: 90636b5d-0d57-483c-bbfd-c0cdab2adaaa$
Status: Started$
Number of Bricks: 2 x 2 = 4$
Transport-type: tcp$
Bricks:$
Brick1: srv18.trollweb.net:/srv/gluster/brick0$
Brick2: srv17.trollweb.net:/srv/gluster/brick0$
Brick3: srv18.trollweb.net:/srv/gluster/brick1$
Brick4: srv17.trollweb.net:/srv/gluster/brick1$
--
Vennlig hils...
2015 Aug 31
2
Libvirt resume guest startup issues centos 7
...r0
TYPE=Bridge
BOOTPROTO=dhcp
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=no
IPV6_DEFROUTE=no
IPV6_PEERDNS=no
IPV6_PEERROUTES=no
IPV6_FAILURE_FATAL=no
ONBOOT=yes
# /etc/sysconfig/network-scripts/ifcfg-eno1
#TYPE=Ethernet
NAME=eno1
UUID=b270f0aa-6b68-4870-bbfd-d6da7c5c62c1
DEVICE=eno1
ONBOOT=yes
BRIDGE=br0
# /etc/sysconfig/network-scripts/ifcfg-eno2
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=eno2...
2015 Aug 31
4
Libvirt resume guest startup issues centos 7
Here is the relevant log snippet:
journal: libvirt version: 1.2.8, package: 16.el7_1.3 (CentOS BuildSystem
<http://bugs.centos.org>, 2015-05-12-20:12:58, worker1.bsys.centos.org)
journal: failed to connect to monitor socket: No such process
journal: internal error: process exited while connecting to monitor:
((null):1937): Spice-Warning **: reds.c:3036:reds_init_socket: