search for: fe55

....YY.33.255 , but that''s neither one of them. Does it matter in this case? My current configuration: # ifconfig in dom0: eth0 Link encap:Ethernet HWaddr 00:30:48:55:27:AA inet addr:XX.YY.33.64 Bcast:XX.YY.33.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe55:27aa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1225895 errors:0 dropped:0 overruns:0 frame:0 TX packets:4864 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:77888321 (74.2 MiB) TX by...

...0.3% fragmentation) /dev/da0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1e: clean, 177737 free (1441 frags, 22037 blocks, 0.3% fragmentation) Setting hostname: cwtest. vfs.nfsrv.async: 0 -> 1 ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet6 fe80::240:5ff:fe55:fe74%ed0 prefixlen 64 tentative scopeid 0x1 inet 10.1.1.2 netmask 0xffffff00 broadcast 10.1.1.255 ether 00:40:05:55:fe:74 ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet6 fe80::2e0:29ff:fe7d:840b%ed1 prefixlen 64 tentative scopeid 0x2 inet...

...errors:0 dropped:0 overruns:0 frame:0 TX packets:2652 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:449235 (438.7 KiB) tap1 Link encap:Ethernet HWaddr AA:BB:F6:55:59:5E inet6 addr: fe80::a8bb:f6ff:fe55:595e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:8862 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:60 (60.0 b) TX bytes:878033 (...

...scope link valid_lft forever preferred_lft forever 5: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 13: ath0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 199 link/ether 00:0d:88:55:d2:10 brd ff:ff:ff:ff:ff:ff inet6 fe80::20d:88ff:fe55:d210/64 scope link valid_lft forever preferred_lft forever 16: br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue link/ether 00:0d:88:55:d2:10 brd ff:ff:ff:ff:ff:ff inet 192.168.0.50/24 brd 192.168.0.255 scope global br0 inet6 fe80::20d:88ff:fe55:d210/64 scope link...

Hello everyone, I have setup two Samba AD DC's with BIND9_DLZ dns backend. faiserver.example.corp is one of them hosting all FSMO Roles. location-000001.example.corp is the second one. Both are in different subnets but can reach each other. Unfortunately replication only works from faiserver.example.corp -> location-000001.example.corp. In the other direction location-000001.example.corp

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...1EC3842D6E7ED2887610 (d43105a8-73b1-4ee7-afae-9cb09996b016) on home-client-2 [2017-10-25 10:14:23.314499] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/C6DC7D43D4EB30329947D8FD5C35755E5689943B (8e741233-fe55-4ec7-8569-70054b140c90) on home-client-2 [2017-10-25 10:14:23.333872] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/5E5FD9DE57216833D9BABD290B7E233D6939C9C2 (6bd3accb-579c-4857-955c-dfb454118320) on hom...