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-4425 Lustre <p>This issue was created by maloo for Bob Glossman &lt;bob.glossman@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="http://maloo.whamcloud.com/test_sets/55b7cddc-7304-11e3-9955-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/55b7cddc-7304-11e3-9955-52540035b04c</a>.</p> <p>The sub-test test_28 failed with the following error:</p> <blockquote> <p>check lustre.llite.max_read_ahead_whole_mb failed!</p></blockquote> <p>Info required for matching: conf-sanity 28</p> LU-4425

Test failure on test suite conf-sanity, subtest test_28

Bug Minor Resolved Cannot Reproduce WC Triage Maloo Thu, 2 Jan 2014 15:51:17 +0000 Fri, 16 May 2014 19:47:30 +0000 Fri, 16 May 2014 19:47:30 +0000 0 5 <p>To repeat what was posted on <a href="https://jira.whamcloud.com/browse/LU-3319" title="Adapt to 3.10 upstream kernel proc_dir_entry change" class="issue-link" data-issue-key="LU-3319"><del>LU-3319</del></a>.</p> <p>Test conf-sanity 28 fails 4% of time with the following error.</p> <p>LustreError: 18595:0:(lproc_llite.c:367:ll_max_read_ahead_whole_mb_seq_write()) can't set max_read_ahead_whole_mb more than max_read_ahead_per_file_mb: 0<br/> LustreError: 18595:0:(obd_config.c:1443:class_process_proc_seq_param()) writing proc entry max_read_ahead_whole_mb err -34</p> <p>Looking at the code this means the variable ra_max_pages is being set to zero. Looking at llite_lib.c<br/> we see that</p> <p>pages = si.totalram - si.totalhigh;<br/> ...<br/> sbi-&gt;ll_ra_info.ra_max_pages_per_file = min(pages / 32,<br/> SBI_DEFAULT_READAHEAD_MAX);</p> <p>so for some reason si_meminfo() is reporting no free memory.</p> <p>Possible idea is for test 28 to set max_readahead_per_file_mb before the test start since this is the reason for the test fails.</p> <p>meminfo can report 0 memory if memory is exhausted. Memory is a limited resource and the kernel keeps the last little bit protected. Are there any other signs of memory pressure on the system?</p> <p>Is there any correlation between the test failures and running on SLES clients? I'm wondering if there is any chance that this could be related to seq_file changes somehow?</p> <p>This is showing up with an earlier patch for 7290. Waiting to see if the new patch has this problem still.</p> <p>This problems seems to have gone away. We can close this ticket if that is the case but can be reopen if the problem appears again.</p> <p>Does this problem still happen? If not can we close this ticket.</p> <p>llite proc bug no longer shows up. Peter you can close this ticket.</p> <p>As you wish <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> Development Rank 1|hzwc1z: Rank (Obsolete) 12154 Severity