<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:29:58 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-2985] e2fsck fails and aborted if it generates the database for lfsck</title>
                <link>https://jira.whamcloud.com/browse/LU-2985</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;The customer&apos;s MDT crashed and they ran e2fsck and a lot of problem couldn&apos;t be fixed. They upgraded e2fsck to latest version and fixed corruptions with it and they are now going to lfsck before mount MDT.&lt;/p&gt;

&lt;p&gt;However, when they ran e2fsck to generage database, we saw the following error messages and can&apos;t generate database from MDT.&lt;/p&gt;

&lt;p&gt;/sbin/e2fsck -n -v --mdsdb /tmp/mdsdb /dev/ExHwRaid10VolGroup/mdt&lt;/p&gt;

&lt;p&gt;MDS: got 4168 bytes = 521 entries in lov_objids&lt;br/&gt;
MDS: max_files = 288784110&lt;br/&gt;
MDS: num_osts = 521&lt;br/&gt;
mds info db file written&lt;br/&gt;
db-&amp;gt;put failed&lt;br/&gt;
: DB_KEYEXIST: Key/data pair already exists&lt;br/&gt;
e2fsck: aborted&lt;/p&gt;</description>
                <environment>Lustre-2.1.0 CentOS5.5</environment>
        <key id="18000">LU-2985</key>
            <summary>e2fsck fails and aborted if it generates the database for lfsck</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.whamcloud.com/images/icons/priorities/critical.svg">Critical</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="2">Won&apos;t Fix</resolution>
                                        <assignee username="niu">Niu Yawei</assignee>
                                    <reporter username="ihara">Shuichi Ihara</reporter>
                        <labels>
                    </labels>
                <created>Tue, 19 Mar 2013 02:25:08 +0000</created>
                <updated>Tue, 19 Mar 2013 13:24:23 +0000</updated>
                            <resolved>Tue, 19 Mar 2013 13:24:23 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="54334" author="yong.fan" created="Tue, 19 Mar 2013 03:20:20 +0000"  >&lt;p&gt;Ihara, are there more logs can be used?&lt;/p&gt;</comment>
                            <comment id="54335" author="niu" created="Tue, 19 Mar 2013 03:25:20 +0000"  >&lt;p&gt;Apparently there is old data in the db which has duplicated key? Does removing the old db and rerun lfsck works?&lt;/p&gt;</comment>
                            <comment id="54336" author="ihara" created="Tue, 19 Mar 2013 03:37:51 +0000"  >&lt;p&gt;Niu, FanYong&lt;br/&gt;
They removed /tmp/mdsdb every time before run e2fsck for generating database.&lt;br/&gt;
what logs files do you want to see? &lt;/p&gt;</comment>
                            <comment id="54337" author="ihara" created="Tue, 19 Mar 2013 03:41:31 +0000"  >&lt;p&gt;it&apos;s log file when they ran e2fsck to generate database.&lt;/p&gt;</comment>
                            <comment id="54338" author="ihara" created="Tue, 19 Mar 2013 03:42:24 +0000"  >&lt;p&gt;just attached e2fsck log.&lt;/p&gt;</comment>
                            <comment id="54351" author="niu" created="Tue, 19 Mar 2013 08:08:04 +0000"  >&lt;p&gt;seems like there are duplicated inode number on the local mds filesystem, did you run &apos;e2fsck -f&apos; to fix the local filesystem before generating mds db?&lt;/p&gt;</comment>
                            <comment id="54357" author="adilger" created="Tue, 19 Mar 2013 09:16:50 +0000"  >&lt;p&gt;For 2.x lfsck, it is using the FID as the key for the mdsdb.  I don&apos;t think there could be duplicate inode numbers in the filesystem, but it is possible that lfsck isn&apos;t handling hard links correctly?&lt;/p&gt;

&lt;p&gt;If the customer has run e2fsck on the MDS filesystem, it isn&apos;t strictly necessary to run lfsck.  Until this problem with lfsck is better understood, they should be able to use the filesystem without lfsck.&lt;/p&gt;</comment>
                            <comment id="54365" author="pjones" created="Tue, 19 Mar 2013 13:24:23 +0000"  >&lt;p&gt;Please cease all work on this. This is for an unsupported site running and unsupported version of Lustre.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="12402" name="e2fsck-mdsdb-output" size="17051" author="ihara" created="Tue, 19 Mar 2013 03:41:31 +0000"/>
                    </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|hzvlnj:</customfieldvalue>

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

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