[Bugs] [Bug 1554509] DHT errors in FUSE mount when using 4.0.0 client bits

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1554509



--- Comment #1 from Raghavendra G <rgowdapp at redhat.com> ---
(In reply to Shyamsundar from comment #0)
> Description of problem:
> 
> Upgraded a 3.12 3 servers + 1 client setup to a 4.0.0 version and noticed
> the following errors in the client mount logs,
> 
> NOTE: not sure if a fresh 4.0.0 setup also gives the same errors, but the
> upgrade case did.
> 
> 
> Post upgrade, client mount is seeing this error
> I [MSGID: 109005] [dht-selfheal.c:2328:dht_selfheal_directory] 0-patchy-dht:
> Directory selfheal failed: Unable to form layout for directory /
> 
> and, this message
> I [MSGID: 109063] [dht-layout.c:693:dht_layout_normalize] 0-patchy-dht:
> Found anomalies in (null) (gfid = 00000000-0000-0000-0000-000000000000).
> Holes=1 overlaps=0

This is a false positive of an error. These errors are normally seen when a
lookup races with mkdir and finds a directory with layout _yet_ to be set. IOW,
its a transient condition which gets resolved once either mkdir or lookup
completes.

> 
> Inspection of brick root on the servers, shows a proper layout that is fully
> formed,
> # getfattr -d  -e hex -m . /d/brick1     
> getfattr: Removing leading '/' from absolute path names
> # file: d/brick1
> security.
> selinux=0x73797374656d5f753a6f626a6563745f723a6574635f72756e74696d655f743a733
> 000
> trusted.afr.dirty=0x000000000000000000000000
> trusted.afr.patchy-client-1=0x000000000000000000000000
> trusted.afr.patchy-client-2=0x000000000000000000000000
> trusted.gfid=0x00000000000000000000000000000001
> trusted.glusterfs.dht=0x000000010000000000000000ffffffff
> trusted.glusterfs.volume-id=0xb43003c35dde4cf0915ac7d9ac94764e
> 
> Version-Release number of selected component (if applicable):
> 4.0.0
> 
> How reproducible:
> Always
> 
> Steps to Reproduce:
> Setup a cluster using docker containers as detailed here:
> https://hackmd.io/-yC3Ol68SwaRWr8bzaL8pw#
> 
> 
> Actual results:
> None of the operations failed, the logs were having the above messages, even
> after a remount on the client.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.