[Bugs] [Bug 1385104] invalid argument warning messages seen in fuse client logs 2016-09-30 06: 34:58.938667] W [dict.c:418ict_set] (-->/usr/lib64/glusterfs/3.8.4/xlator/ cluster/replicate.so(+0x58722) 0-dict: !this || !value for key= link-count [Invalid argument]

[bugzilla at redhat.com]

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



--- Comment #1 from Pranith Kumar K <pkarampu at redhat.com> ---
Steps to reproduce this:
1. Create a 2x2 volume. 
2. Fuse mount the volume and create dir1
3. Unmount volume
4. Delete dir1 manually on both bricks of any one replica set.
5. Mount the volume and do a lookup. DHT should see that the directory is
missing and trigger a heal, causing this message to be logged.

Following logs are seen about Invalid argument
client Logs:
[2016-09-30 06:34:58.938667] W [dict.c:418ict_set]
(-->/usr/lib64/glusterfs/3.8.4/xlator/cluster/replicate.so(+0x58722)
[0x7f7a1c50f722] -->/usr/lib64/libglusterfs.so.0(dict_set_str+0x3c)
[0x7f7a2a3d178c] -->/usr/lib64/libglusterfs.so.0(dict_set+0x113)
[0x7f7a2a3d0bc3] ) 0-dict: !this || !value for key=link-count [Invalid
argument]
[2016-09-30 06:34:58.949023] E [MSGID: 114031]
[client-rpc-fops.c:1550:client3_3_inodelk_cbk] 0-distrepvol-client-7: remote
operation failed [Invalid argument]
[2016-09-30 06:34:59.178135] I [MSGID: 109063]
[dht-layout.c:713ht_layout_normalize] 0-distrepvol-dht: Found anomalies in
/rootdir1/renames/dir_samenames/level1.1/level2.1/level3.21/level4.17/level5.13
(gfid = 6bd93a82-7c5e-47d4-9f7d-5e703a1225d6). Holes=1 overlaps=0
[2016-09-30 06:35:01.301329] W [fuse-bridge.c:471:fuse_entry_cbk]
0-glusterfs-fuse: 27400471: MKDIR()
/rootdir1/renames/dir_samenames/level1.1/level2.1/level3.21/level4.17/level5.24
=> -1 (File exists)
[2016-09-30 06:35:01.371991] I [MSGID: 109063]
[dht-layout.c:713ht_layout_normalize] 0-distrepvol-dht: Found anomalies in
/rootdir1/renames/dir_samenames/level1.1/level2.1/level3.21/level4.17/level5.24
(gfid = 310d4874-bcc5-442f-a378-265004540333). Holes=1 overlaps=0

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