search for: 46ea

...w2 format and set the shareable properties in the disk driver like this: <disk type='block' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source dev='/dev/81035c32-d2e4-4aaf-82fa-3e76ae587586/ca18f6a5-7c98-46ea-b562-9424e68a52f3'/> <target dev='hda' bus='ide'/> <shareable/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> But when we use it as shared data disk like we use...

...n the disk >> driver like this: >> >> <disk type='block' device='disk'> >> <driver name='qemu' type='qcow2' cache='none'/> >> <source dev='/dev/81035c32-d2e4-4aaf-82fa-3e76ae587586/ca18f6a5-7c98-46ea-b562-9424e68a52f3'/> >> <target dev='hda' bus='ide'/> >> <shareable/> >> <address type='drive' controller='0' bus='0' target='0' unit='0'/> >> </disk> >> >&g...

...areable properties in the disk > driver like this: > > <disk type='block' device='disk'> > <driver name='qemu' type='qcow2' cache='none'/> > <source dev='/dev/81035c32-d2e4-4aaf-82fa-3e76ae587586/ca18f6a5-7c98-46ea-b562-9424e68a52f3'/> > <target dev='hda' bus='ide'/> > <shareable/> > <address type='drive' controller='0' bus='0' target='0' unit='0'/> > </disk> > > But when we use it as...

...gt; driver like this: >>> >>> <disk type='block' device='disk'> >>> <driver name='qemu' type='qcow2' cache='none'/> >>> <source dev='/dev/81035c32-d2e4-4aaf-82fa-3e76ae587586/ca18f6a5-7c98-46ea-b562-9424e68a52f3'/> >>> <target dev='hda' bus='ide'/> >>> <shareable/> >>> <address type='drive' controller='0' bus='0' target='0' unit='0'/> >>> </disk>...

...ying the version and platform information for XAPI? My xensource-inventory file looks fine: BUILD_NUMBER=''61809c'' SOFTWARE_VERSION=''1.6.10'' DOM0_MEM=''752'' MANAGEMENT_INTERFACE=''xenbr0'' INSTALLATION_UUID=''718e7db1-cf3d-46ea-bcc9-cee8c456ed4d'' COMPANY_NAME_SHORT=''xen.org'' PLATFORM_NAME=''XCP'' PLATFORM_VERSION=''1.6.10'' KERNEL_VERSION=''2.6.32.43-0.4.1.xs1.6.10.734.170748xen'' BRAND_CONSOLE=''a console'' COMPANY_NAME=''x...

...eplicate from location-000001.domain.de to location-000002.domain.de was successful.root at location-000001.domain.de: samba-tool drs showrepl -k yes Default-First-Site-Name\LOCATION-000001 DSA Options: 0x00000001 DSA object GUID: 2cb772ba-41ef-450f-bd04-706c5e21fbc7 DSA invocationId: 6726b0b3-edc3-46ea-9d97-a1aea14b20ec ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=domain,DC=de Default-First-Site-Name\LOCATION-000002 via RPC DSA object GUID: 1204a63a-c247-42f0-8144-68ab35632e03 Last attempt @ Sat Apr 6 08:28:19 2019 UTC failed, result 1326 (WERR_LOGON_FAILURE) 160 consecutive failure...

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

...common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on f82d1046-4fc9-4b7e-b969-20b7b3241e0b. sources=0 [2] sinks=1 [2017-10-25 10:40:30.566795] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on 7a2465ff-c747-46ea-92d3-8a5e108965c4. sources=0 [2] sinks=1 [2017-10-25 10:40:30.571040] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on bdb55228-47d8-4eff-a201-8321123daf5c [2017-10-25 10:40:30.573725] I [MSGID: 108026] [afr-self-heal-c...