<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:43:30 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-11395] conf-sanity test 99 fails with &apos;add ost1 failed with new params - group descriptors corrupted!&apos;</title>
                <link>https://jira.whamcloud.com/browse/LU-11395</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;conf-sanity test_99 started failing on 2018-09-01 for SLES12 SP3 testing. For the failure at &lt;a href=&quot;https://testing.whamcloud.com/test_sets/dfe70e50-ba62-11e8-a7de-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/test_sets/dfe70e50-ba62-11e8-a7de-52540065bddc&lt;/a&gt;, we see the following in the test_log&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;== conf-sanity test 99: Adding meta_bg option ======================================================== 11:07:52 (1537121272)
CMD: trevis-9vm3 /usr/sbin/lctl get_param -n version 2&amp;gt;/dev/null ||
				/usr/sbin/lctl lustre_build_version 2&amp;gt;/dev/null ||
				/usr/sbin/lctl --version 2&amp;gt;/dev/null | cut -d&apos; &apos; -f2
CMD: trevis-9vm3 debugfs -c -R stats /dev/mapper/ost1_flakey
trevis-9vm3: debugfs 1.42.13.wc6 (05-Feb-2017)
trevis-9vm3: /dev/mapper/ost1_flakey: catastrophic mode - not reading inode or group bitmaps
params: --mgsnode=trevis-9vm4@tcp --fsname=lustre --ost 			--index=0 --param=sys.timeout=20 --backfstype=ldiskfs --device-size=200000  		--mkfsoptions=\&quot;-O ^resize_inode,meta_bg -E lazy_itable_init\&quot; 		--reformat /dev/mapper/ost1_flakey 
CMD: trevis-9vm3 grep -c /mnt/lustre-ost1&apos; &apos; /proc/mounts || true
CMD: trevis-9vm3 lsmod | grep lnet &amp;gt; /dev/null &amp;amp;&amp;amp;
lctl dl | grep &apos; ST &apos; || true
CMD: trevis-9vm3 mkfs.lustre --mgsnode=trevis-9vm4@tcp --fsname=lustre --ost --index=0 --param=sys.timeout=20 --backfstype=ldiskfs --device-size=200000 --mkfsoptions=\&quot;-O ^resize_inode,meta_bg -E lazy_itable_init\&quot; --reformat /dev/mapper/ost1_flakey
trevis-9vm3: mkfs.lustre: Unable to mount /dev/mapper/ost1_flakey: Structure needs cleaning
trevis-9vm3: 
trevis-9vm3: mkfs.lustre FATAL: failed to write local files
trevis-9vm3: mkfs.lustre: exiting with 117 (Structure needs cleaning)

   Permanent disk data:
Target:     lustre:OST0000
Index:      0
Lustre FS:  lustre
Mount type: ldiskfs
Flags:      0x62
              (OST first_time update )
Persistent mount opts: ,errors=remount-ro
Parameters: mgsnode=10.9.4.97@tcp sys.timeout=20

device size = 2048MB
formatting backing filesystem ldiskfs on /dev/mapper/ost1_flakey
	target name   lustre:OST0000
	4k blocks     50000
	options         -I 512 -q -O ^resize_inode,meta_bg,extents,uninit_bg,dir_nlink,quota,huge_file,flex_bg -G 256 -E lazy_itable_init,lazy_journal_init -F
mkfs_cmd = mke2fs -j -b 4096 -L lustre:OST0000   -I 512 -q -O ^resize_inode,meta_bg,extents,uninit_bg,dir_nlink,quota,huge_file,flex_bg -G 256 -E lazy_itable_init,lazy_journal_init -F /dev/mapper/ost1_flakey 50000
 conf-sanity test_99: @@@@@@ FAIL: add ost1 failed with new params 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;In the OST (vm3) console log, we see&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;[37266.504045] Lustre: DEBUG MARKER: mkfs.lustre --mgsnode=trevis-9vm4@tcp --fsname=lustre --ost --index=0 --param=sys.timeout=20 --backfstype=ldiskfs --device-size=200000 --mkfsoptions=&quot;-O ^resize_inode,meta_bg -E lazy_itable_init&quot; --reformat /dev/mapper/ost1_flakey
[37266.683422] LDISKFS-fs (dm-11): ldiskfs_check_descriptors: Block bitmap for group 0 overlaps block group descriptors
[37266.683428] LDISKFS-fs (dm-11): group descriptors corrupted!
[37266.789545] Lustre: DEBUG MARKER: /usr/sbin/lctl mark  conf-sanity test_99: @@@@@@ FAIL: add ost1 failed with new params 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;After the conf-sanity test 99 failure, conf-sanity test_100, 101, 102, 104, 1-5, 106, 107, 108b, 109a, 109b, and 122 all fail with &lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Kernel error detected: [37266.683428] LDISKFS-fs (dm-11): group descriptors corrupted!
 conf-sanity test_100: @@@@@@ FAIL: Error in dmesg detected 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;In many of the test sessions that we see conf-sanity test 99 fail, we also see racer test 1 and replay-single 0a, 0b, 0c also fail with corrupted group descriptors. &lt;/p&gt;

&lt;p&gt;conf-sanity test 99 started failing with this error on 2018-09-01 and have seen it several times for SUSE 12 SP3 client and server testing. Some failures are at:&lt;br/&gt;
&lt;a href=&quot;https://testing.whamcloud.com/test_sets/561cf376-ae44-11e8-bd05-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/test_sets/561cf376-ae44-11e8-bd05-52540065bddc&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://testing.whamcloud.com/test_sets/58fb8682-b09e-11e8-80f7-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/test_sets/58fb8682-b09e-11e8-80f7-52540065bddc&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://testing.whamcloud.com/test_sets/d657ba78-b63a-11e8-b86b-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/test_sets/d657ba78-b63a-11e8-b86b-52540065bddc&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://testing.whamcloud.com/test_sets/76f11f72-b921-11e8-9df3-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/test_sets/76f11f72-b921-11e8-9df3-52540065bddc&lt;/a&gt;&lt;/p&gt;</description>
                <environment>SUSE12 SP3</environment>
        <key id="53345">LU-11395</key>
            <summary>conf-sanity test 99 fails with &apos;add ost1 failed with new params - group descriptors corrupted!&apos;</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="3">Duplicate</resolution>
                                        <assignee username="yujian">Jian Yu</assignee>
                                    <reporter username="jamesanunez">James Nunez</reporter>
                        <labels>
                            <label>sles12</label>
                            <label>suse</label>
                    </labels>
                <created>Tue, 18 Sep 2018 15:40:35 +0000</created>
                <updated>Wed, 19 Dec 2018 21:16:08 +0000</updated>
                            <resolved>Wed, 26 Sep 2018 07:29:57 +0000</resolved>
                                    <version>Lustre 2.12.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="233693" author="simmonsja" created="Tue, 18 Sep 2018 16:53:15 +0000"  >&lt;p&gt;I wonder if&#160; &lt;a href=&quot;https://review.whamcloud.com/#/c/33144&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/#/c/33144&lt;/a&gt;&#160;would help here?&lt;/p&gt;</comment>
                            <comment id="233758" author="green" created="Wed, 19 Sep 2018 17:26:35 +0000"  >&lt;p&gt;no, that ubuntu patch is not used for sles builds, unless you mean if there&apos;s a similar problem there?&lt;/p&gt;</comment>
                            <comment id="233759" author="pjones" created="Wed, 19 Sep 2018 17:29:18 +0000"  >&lt;p&gt;Jian&lt;/p&gt;

&lt;p&gt;This seems to line up with when the kernel update landed. Could you please investigate?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="233904" author="yujian" created="Sun, 23 Sep 2018 07:03:53 +0000"  >&lt;p&gt;After updating SLES12 SP3 kernel to version 4.4.155-94.50.1, conf-sanity test 99 passed:&lt;br/&gt;
&lt;a href=&quot;https://testing.whamcloud.com/sub_tests/c3fce2da-be5b-11e8-a9d9-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/sub_tests/c3fce2da-be5b-11e8-a9d9-52540065bddc&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I&apos;m investigating the conf-sanity test 103 and sanity-sec test failures and will resolve the issues in the patch for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11412&quot; title=&quot;kernel update [SLES12 SP3 4.4.155-94.50.1]&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11412&quot;&gt;&lt;del&gt;LU-11412&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="233999" author="yujian" created="Wed, 26 Sep 2018 07:29:18 +0000"  >&lt;p&gt;It turns out conf-sanity test 103 is a known issue on master branch and tracked in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11196&quot; title=&quot;conf-sanity test_103: Fail to cleanup the env&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11196&quot;&gt;&lt;del&gt;LU-11196&lt;/del&gt;&lt;/a&gt;.&lt;br/&gt;
conf-sanity test 99 failure will be fixed in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11412&quot; title=&quot;kernel update [SLES12 SP3 4.4.155-94.50.1]&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11412&quot;&gt;&lt;del&gt;LU-11412&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="53380">LU-11412</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i002mn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>