https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-2951 Lustre <p>This issue was created by maloo for Li Wei &lt;liwei@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/9e87cad2-8b22-11e2-965f-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/9e87cad2-8b22-11e2-965f-52540035b04c</a>.</p> <p>The sub-test test_102ha failed with the following error:</p> <blockquote> <p>test failed to respond and timed out</p></blockquote> <p>Info required for matching: sanity 102ha</p> <p>The MDS was dropping requests, while the client was repeatedly reconnecting until Autotest timed out:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>10:38:21:LNetError: 3022:0:(lib-ptl.c:190:lnet_try_match_md()) Matching packet from 12345-10.10.17.9@tcp, match 1429230968490588 length 65928 too big: 117674 left, 49386 allowed 10:39:14:Lustre: lustre-MDT0000: Client 8aa83ecb-c95c-6b87-53ec-3d81990549d0 (at 10.10.17.9@tcp) reconnecting </pre> </div></div> LU-2951

lnet_try_match_md()) Matching packet from 12345-10.10.17.9@tcp, match 1429230968490588 length 65928 too big: 117674 left, 49386 allowed

Bug Blocker Closed Fixed Li Wei Maloo HB Tue, 12 Mar 2013 21:00:16 +0000 Tue, 26 Mar 2013 04:53:09 +0000 Tue, 26 Mar 2013 04:52:58 +0000 Lustre 2.4.0 Lustre 2.4.0 0 6 <p><a href="https://maloo.whamcloud.com/test_sets/d32b51c6-8b24-11e2-965f-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/d32b51c6-8b24-11e2-965f-52540035b04c</a></p> <p>This time it was conf-sanity 58b.</p> <p>This is due to recent request buffer shrinking effort, which makes SETXATTR unable to accept requests with maximum extend attribute size (64 KB). 49386 is exactly current intended max size for SETXATTR, while 65928 is how much needed.</p> <p><a href="https://maloo.whamcloud.com/test_sets/d89abf3a-884e-11e2-961a-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/d89abf3a-884e-11e2-961a-52540035b04c</a></p> <p>Another example of this issue for sanity test_102ha</p> <p>ZFS, conf-sanity test_61</p> <p><a href="https://maloo.whamcloud.com/test_sets/fba5bc00-8bb9-11e2-aa89-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/fba5bc00-8bb9-11e2-aa89-52540035b04c</a></p> <p><a href="http://review.whamcloud.com/5703" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5703</a></p> <p>Looks like this is mostly hitting on review-zfs because ZFS has "large xattr" enabled by default, but that isn't currently enabled for ldiskfs by default, but the bug would be applicable to both.</p> <p>We should really squash the last remaining ZFS test failures and enable ZFS testing for real, so we don't keep introducing failures like this that are not caught "because ZFS tests always fail"...</p> <p>The patch above has landed on master.</p> Development Rank 1|hzvkon: Rank (Obsolete) 7084 Severity