[LU-3938] Test failure on test suite conf-sanity, test_61: getxattr failed: -34 Created: 12/Sep/13  Updated: 23/Sep/13  Resolved: 23/Sep/13

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.5.0
Fix Version/s: Lustre 2.5.0

Type: Bug Priority: Critical
Reporter: Maloo Assignee: Nathaniel Clark
Resolution: Fixed Votes: 0
Labels: revzfs, zfs

Issue Links:
Related
is related to LU-3669 (mdt_xattr.c:178:mdt_getxattr()) ASSE... Closed
is related to LU-3792 Failure conf-sanity, test_61, error: ... Closed
is related to LU-3793 conf-sanity, subtest test_66 fails du... Resolved
Severity: 3
Rank (Obsolete): 10415

 Description   

This issue was created by maloo for Nathaniel Clark <nathaniel.l.clark@intel.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/62d75ef0-1b8f-11e3-ae29-52540035b04c.

The sub-test test_61 failed with the following error:

trusted.big different after shrinking

Info required for matching: conf-sanity 61

This issue is related to LU-3792, but is post LU-3669 patch

MDS console log:

22:54:33:Lustre: DEBUG MARKER: save large xattr trusted.big on /mnt/lustre/f.conf-sanity.61
22:54:33:LustreError: 16198:0:(mdt_xattr.c:134:mdt_getxattr_one()) getxattr failed: -34
22:54:33:LustreError: 16197:0:(mdt_xattr.c:134:mdt_getxattr_one()) getxattr failed: -34


 Comments   
Comment by Nathaniel Clark [ 13/Sep/13 ]

Looking at the wireshark dump of the traffic between the MDT and the Client, it appears that the trusted.big xattr is actually created twice on the MDT (judging by the fact that listxattr returns it twice from the MDT). Thus causing the "Protocol error" on the client.

Comment by Nathaniel Clark [ 16/Sep/13 ]

Remount MDT as ZFS:

[root@lumgr1 mdt1]# getfattr -m - ROOT/f.conf-sanity.61 
# file: ROOT/f.conf-sanity.61
trusted.big
trusted.big
trusted.link
trusted.lma
trusted.lov

Comment by Nathaniel Clark [ 16/Sep/13 ]

http://review.whamcloud.com/7671

Comment by Peter Jones [ 23/Sep/13 ]

Landed for 2.5.0

Generated at Sat Feb 10 01:38:13 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.