Bug 1567169 - getting "Mismatching layouts" messages on client logs
Summary: getting "Mismatching layouts" messages on client logs
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: distribute
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nithya Balachandran
QA Contact: Prasad Desala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-13 13:59 UTC by Nag Pavan Chilakam
Modified: 2018-04-13 14:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-13 14:51:56 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Nag Pavan Chilakam 2018-04-13 13:59:17 UTC
Description of problem:
--------------------
due to the newly added consumption of first few bits in the dht xattrs, it seems like we are seeing below messages on client logs, which can confuse admins

[2018-04-13 14:00:38.051145] I [MSGID: 109064] [dht-layout.c:837:dht_layout_dir_mismatch] 0-zen-dht: subvol: zen-disperse-0; inode layout - 0 - 2147483646 - 0; disk layout - 0 - 2147483646 - 3599082329
[2018-04-13 14:00:38.051191] I [MSGID: 109018] [dht-common.c:1685:dht_revalidate_cbk] 0-zen-dht: Mismatching layouts for /folder1, gfid = b7163338-0fc7-4dbf-b855-2708e1b6e40c
[2018-04-13 14:00:38.051216] I [MSGID: 109064] [dht-layout.c:837:dht_layout_dir_mismatch] 0-zen-dht: subvol: zen-disperse-1; inode layout - 2147483647 - 4294967295 - 0; disk layout - 2147483647 - 4294967295 - 3599082329
[2018-04-13 14:00:38.051240] I [MSGID: 109018] [dht-common.c:1685:dht_revalidate_cbk] 0-zen-dht: Mismatching layouts for /folder1, gfid = b7163338-0fc7-4dbf-b855-2708e1b6e40c





[root@dhcp35-205 log]# getfattr -d -m . -e hex /gluster/brick*/zen/folder1
getfattr: Removing leading '/' from absolute path names
# file: gluster/brick1/zen/folder1
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.ec.version=0x00000000000000000000000000000001
trusted.gfid=0xb71633380fc74dbfb8552708e1b6e40c
trusted.glusterfs.dht=0x0000000000000000000000007ffffffe

# file: gluster/brick2/zen/folder1
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.ec.version=0x00000000000000000000000000000001
trusted.gfid=0xb71633380fc74dbfb8552708e1b6e40c
trusted.glusterfs.dht=0x00000000000000007fffffffffffffff
trusted.glusterfs.dht.mds=0x00000000


[root@dhcp35-205 log]# getfattr -d -m . -e hex /gluster/brick*/zen/folder1
getfattr: Removing leading '/' from absolute path names
# file: gluster/brick1/zen/folder1
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.ec.version=0x00000000000000020000000000000009
trusted.gfid=0xb71633380fc74dbfb8552708e1b6e40c
trusted.glusterfs.dht=0xd685a35900000000000000007ffffffe
---------------------->talking about above bits "0xd685a35900...."

# file: gluster/brick2/zen/folder1
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.ec.version=0x00000000000000020000000000000009
trusted.gfid=0xb71633380fc74dbfb8552708e1b6e40c
trusted.glusterfs.dht=0xd685a359000000007fffffffffffffff
trusted.glusterfs.dht.mds=0x00000000

[root@dhcp35-205 log]# getfattr -d -m . -e hex /gluster/brick*/zen/folder1/subfolder
getfattr: /gluster/brick*/zen/folder1/subfolder: No such file or directory
[root@dhcp35-205 log]# getfattr -d -m . -e hex /gluster/brick*/zen/folder1/subfolder1
getfattr: Removing leading '/' from absolute path names
# file: gluster/brick1/zen/folder1/subfolder1
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.ec.version=0x00000000000000000000000000000001
trusted.gfid=0x22913ce5d2ea471bb33de8d8ec116f15
trusted.glusterfs.dht=0x0000000000000000000000007ffffffe
trusted.glusterfs.dht.mds=0x00000000

# file: gluster/brick2/zen/folder1/subfolder1
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.ec.version=0x00000000000000000000000000000001
trusted.gfid=0x22913ce5d2ea471bb33de8d8ec116f15
trusted.glusterfs.dht=0x00000000000000007fffffffffffffff

Version-Release number of selected component (if applicable):


How reproducible:
-----------------
always

Steps to Reproduce:
1.had my setup after hitting BZ#1567100 
2.did a rebalance and waited for it complete
3.create a new dir ie folder1 ,and saw errors in client as mentioned in bz#1567129
4. retriggered rebalance and waited for completion
5. now created a dir under existing dir ie mkdir folder1/subfolder1
and am seeing above messages in fuse client logs


this can confuse users and also , would mean that any new dirs created under existing dirs post rebalance would flood the logs


Note You need to log in before you can comment on or make changes to this bug.