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-4348 Lustre <p>This issue was created by maloo for sarah &lt;sarah@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="http://maloo.whamcloud.com/test_sets/20748e4e-5c66-11e3-9d08-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/20748e4e-5c66-11e3-9d08-52540035b04c</a>.</p> <p>The sub-test test_82 failed with the following error:</p> <blockquote> <p>test_82 failed with 61</p></blockquote> <p>test log</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>== sanity test 82: Basic grouplock test ================================= 19:16:14 (1386040574) dd: writing `/mnt/lustre/f.sanity.82': No space left on device </pre> </div></div> lustre-master build #1791 RHEL6 zfs LU-4348

Failure on test suite sanity test_82: no space left

Bug Major Resolved Fixed WC Triage Maloo zfs Thu, 5 Dec 2013 07:35:45 +0000 Thu, 19 Feb 2015 20:03:23 +0000 Thu, 19 Feb 2015 20:03:23 +0000 Lustre 2.6.0 0 5 <p>In the latest tag-2.5.52 zfs testing, hit a lot similar errors as "no space left on device". I checked the lustre-initialization_1 log and found, both MDS size and OST size are smaller than the previous tag-2.5.51</p> <p>in 2.5.52, lustre-initialization_1 autotest log shows:<br/> <a href="https://maloo.whamcloud.com/test_logs/7442b9b4-5c6c-11e3-9d08-52540035b04c/show_text" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_logs/7442b9b4-5c6c-11e3-9d08-52540035b04c/show_text</a></p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>02:17:39:export MDSSIZE=1939865 02:17:40:export MGSSIZE=1939865 02:17:41:export MDSFSTYPE=zfs 02:17:42:export MGSFSTYPE=zfs 02:17:42:export MGSNID=`h2tcp client-26vm7` 02:17:43:export ost_HOST=client-26vm8 02:17:44:export ost1_HOST=client-26vm8 02:17:44:export OSTDEV1=/dev/lvm-Role_OSS/P1 02:17:44:export ost2_HOST=client-26vm8 02:17:45:export OSTDEV2=/dev/lvm-Role_OSS/P2 02:17:45:export ost3_HOST=client-26vm8 02:17:45:export OSTDEV3=/dev/lvm-Role_OSS/P3 02:17:45:export ost4_HOST=client-26vm8 02:17:46:export OSTDEV4=/dev/lvm-Role_OSS/P4 02:17:46:export ost5_HOST=client-26vm8 02:17:46:export OSTDEV5=/dev/lvm-Role_OSS/P5 02:17:46:export ost6_HOST=client-26vm8 02:17:46:export OSTDEV6=/dev/lvm-Role_OSS/P6 02:17:47:export ost7_HOST=client-26vm8 02:17:48:export OSTDEV7=/dev/lvm-Role_OSS/P7 02:17:48:# some setup for conf-sanity test 24a, 24b, 33a 02:17:48:export fs2mds_DEV=/dev/lvm-Role_MDS/S1 02:17:48:export fs2ost_DEV=/dev/lvm-Role_OSS/S1 02:17:48:export fs3ost_DEV=/dev/lvm-Role_OSS/S2 02:17:49:export RCLIENTS="client-26vm1" 02:17:50:export OSTCOUNT=7 02:17:50:export NETTYPE=tcp 02:17:50:export OSTSIZE=223196 </pre> </div></div> <p>in tag 2.5.51 autotest log shows:<br/> <a href="https://maloo.whamcloud.com/test_logs/707fd738-4bc5-11e3-a7be-52540035b04c/show_text" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_logs/707fd738-4bc5-11e3-a7be-52540035b04c/show_text</a></p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>19:47:47:export MDSSIZE=2097152 19:47:48:export MGSSIZE=2097152 19:47:48:export MDSFSTYPE=zfs 19:47:48:export MGSFSTYPE=zfs 19:47:48:export MGSNID=`h2tcp client-13vm3` 19:47:48:export ost_HOST=client-13vm4 19:47:48:export ost1_HOST=client-13vm4 19:47:48:export OSTDEV1=/dev/lvm-Role_OSS/P1 19:47:49:export ost2_HOST=client-13vm4 19:47:49:export OSTDEV2=/dev/lvm-Role_OSS/P2 19:47:49:export ost3_HOST=client-13vm4 19:47:49:export OSTDEV3=/dev/lvm-Role_OSS/P3 19:47:49:export ost4_HOST=client-13vm4 19:47:49:export OSTDEV4=/dev/lvm-Role_OSS/P4 19:47:49:export ost5_HOST=client-13vm4 19:47:49:export OSTDEV5=/dev/lvm-Role_OSS/P5 19:47:49:export ost6_HOST=client-13vm4 19:47:49:export OSTDEV6=/dev/lvm-Role_OSS/P6 19:47:49:export ost7_HOST=client-13vm4 19:47:49:export OSTDEV7=/dev/lvm-Role_OSS/P7 19:47:49:# some setup for conf-sanity test 24a, 24b, 33a 19:47:49:export fs2mds_DEV=/dev/lvm-Role_MDS/S1 19:47:49:export fs2ost_DEV=/dev/lvm-Role_OSS/S1 19:47:49:export fs3ost_DEV=/dev/lvm-Role_OSS/S2 19:47:49:export RCLIENTS="client-13vm2" 19:47:49:export OSTCOUNT=7 19:47:49:export NETTYPE=tcp 19:47:49:export OSTSIZE=2097152 19:47:49:export OSTFSTYPE=zfs </pre> </div></div> <p>I also checked the MDT and OST size for review-zfs, and it is bigger than the config used in tag-2.5.52</p> <p><a href="https://maloo.whamcloud.com/test_logs/9173c588-610c-11e3-974e-52540035b04c/show_text" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_logs/9173c588-610c-11e3-974e-52540035b04c/show_text</a></p> <p>I don't think the 70MB should make such a difference in the ZFS test results. Are these tests being run in normal review tests, or are they only run with SLOW=no?</p> <p>Most of the tests also run in normal review test and pass, only 4 tests are skipped in review tests.</p> <p>Link to TEI tickets that change OSTCOUNT and OSTSIZE for ZFS tests. Hopefully TEI-1032 will resolve this problem. For debugging, Sarah will make a patch to dump space usage in the error handler ( lfs df, lfs df -i, lfs find $MOUNT -size +4M, and grant usage of the client OSCs and OSTs)</p> <p>This seems to be fixed. It hasn't recurred since TEI-1032 was closed (over a year ago)</p> Related Development Rank 1|hzwaqf: Rank (Obsolete) 11913 Severity