<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:22:20 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-2097] sanity.sh test_17m, lfsck: e2fsck failed due to MDT quota accounting error</title>
                <link>https://jira.whamcloud.com/browse/LU-2097</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Running acc-sm on a local ldiskfs test system causes e2fsck to fail when checking the MDT in sanity.sh test_17m.  I&apos;m running e2fsprogs-1.42.5.wc3-7.fc13.x86_64, which I don&apos;t &lt;em&gt;think&lt;/em&gt; is the issue, but it hasn&apos;t been released yet.&lt;/p&gt;

&lt;p&gt;It isn&apos;t clear when the quota accounting issue is first introduced (even if it is present when the filesystem is formatted), but the problem needs to be resolved for 2.4.0 and/or the e2fsprogs-1.42.5.wc3 release.&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;== sanity test 17m: run e2fsck against MDT which contains short/long symlink 21:55:58 (1349409358)
create 512 short and long symlink files under /mnt/testfs/d0.sanity/d17m
erase them
recreate the 512 symlink files with a shorter string
stop and checking mds1: e2fsck -fnvd /dev/vg_sookie/lvmdt1
Stopping /mnt/mds1 (opts:-f) on sookie-gig.adilger.int
e2fsck 1.42.5.wc3 (15-Sep-2012)
[QUOTA WARNING] Usage inconsistent for ID 0:actual (3649536, 1281) != expected (3551232, 1281)
[QUOTA WARNING] Usage inconsistent for ID 0:actual (3645440, 1280) != expected (3547136, 1280)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Update quota info for quota type 0? no

Update quota info for quota type 1? no

testfs-MDT0000: ********** WARNING: Filesystem still has errors **********

        1293 inodes used (1.29%, out of 100000)
           8 non-contiguous files (0.6%)
           1 non-contiguous directory (0.1%)
             # of inodes with ind/dind/tind blocks: 3/0/0
       17587 blocks used (35.17%, out of 50000)
           0 bad blocks
           1 large file

         109 regular files
         135 directories
           0 character device files
           0 block device files
           0 fifos
           8 links
        1040 symbolic links (521 fast symbolic links)
           0 sockets
------------
        1292 files
Starting mds1:   /dev/vg_sookie/lvmdt1 /mnt/mds1
Started testfs-MDT0000
 sanity test_17m: @@@@@@ FAIL: e2fsck should not report error upon  short/long symlink MDT: rc=4 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment>Single node test system (client, MDT, 3x OSTs on same node), x86_64&lt;br/&gt;
Lustre master &amp;quot;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1842&quot; title=&quot;Quota enforcement landing&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1842&quot;&gt;&lt;strike&gt;LU-1842&lt;/strike&gt;&lt;/a&gt; quota: add quotactl support on qmt&amp;quot; (commit 294aa9cb666c48e02da1057c222fe5f206ce38fc)</environment>
        <key id="16264">LU-2097</key>
            <summary>sanity.sh test_17m, lfsck: e2fsck failed due to MDT quota accounting error</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="1" iconUrl="https://jira.whamcloud.com/images/icons/priorities/blocker.svg">Blocker</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="1">Fixed</resolution>
                                        <assignee username="niu">Niu Yawei</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                    </labels>
                <created>Fri, 5 Oct 2012 15:52:43 +0000</created>
                <updated>Fri, 19 Apr 2013 16:20:49 +0000</updated>
                            <resolved>Mon, 29 Oct 2012 05:45:30 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                    <fixVersion>Lustre 2.4.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="46071" author="adilger" created="Fri, 5 Oct 2012 17:57:42 +0000"  >&lt;p&gt;I saw the same problem running mmp.sh test_8 on a newly-formatted MDT filesystem (this is the first test that actually runs e2fsck):&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;Running e2fsck on the device /dev/vg_sookie/lvmdt1 on mds1...
e2fsck 1.42.5.wc3 (15-Sep-2012)
[QUOTA WARNING] Usage inconsistent for ID 0:actual (1294336, 206) != expected (1273856, 206)
[QUOTA WARNING] Usage inconsistent for ID 0:actual (1294336, 206) != expected (1273856, 206)
MMP interval is 30 seconds and total wait time is 122 seconds. Please wait...
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Setting filetype for entry &apos;16&apos; in /O/1/d16 (50023) to 1.
Setting filetype for entry &apos;17&apos; in /O/1/d17 (50024) to 1.
Setting filetype for entry &apos;18&apos; in /O/1/d18 (50025) to 1.
Setting filetype for entry &apos;19&apos; in /O/1/d19 (50026) to 1.
Setting filetype for entry &apos;20&apos; in /O/1/d20 (50027) to 1.
Setting filetype for entry &apos;21&apos; in /O/1/d21 (50028) to 1.
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Update quota info for quota type 0? yes

Update quota info for quota type 1? yes


testfs-MDT0000: ***** FILE SYSTEM WAS MODIFIED *****
testfs-MDT0000: 215/100000 files (2.8% non-contiguous), 17012/50000 blocks
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I can imagine this happening fairly easily if we have code paths that are not updating the root quota usage properly?&lt;/p&gt;

&lt;p&gt;The filetype errors are in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1861&quot; title=&quot;osd-ldiskfs doesn&amp;#39;t set object file type&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1861&quot;&gt;&lt;del&gt;LU-1861&lt;/del&gt;&lt;/a&gt; and not related to this problem.&lt;/p&gt;</comment>
                            <comment id="46074" author="johann" created="Fri, 5 Oct 2012 18:27:45 +0000"  >&lt;p&gt;Andreas, is this with OFD or obdfilter?&lt;/p&gt;</comment>
                            <comment id="46092" author="adilger" created="Sun, 7 Oct 2012 02:11:13 +0000"  >&lt;p&gt;I think I hit it with both ZFS and ldiskfs using OFD, though I don&apos;t &lt;em&gt;think&lt;/em&gt; it matters, since the error is on the MDT?&lt;/p&gt;</comment>
                            <comment id="46098" author="bzzz" created="Sun, 7 Oct 2012 08:08:34 +0000"  >&lt;p&gt;this is rather strange, because we do not modify accounting ?&lt;/p&gt;</comment>
                            <comment id="46101" author="johann" created="Sun, 7 Oct 2012 11:32:32 +0000"  >&lt;blockquote&gt;
&lt;p&gt;I think I hit it with both ZFS and ldiskfs using OFD, though I don&apos;t think it matters, since the error is on the MDT?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Ah, nm. I thought fsck was run against an OST.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;this is rather strange, because we do not modify accounting ?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Right, we don&apos;t, but we still bypass the vfs so there might be a code path where we forget to call ll_vfs_dq_transfer() or something similar. It might also be a bug in quota support in e2fsck or even a kernel bug (till now, nothing was checking accounting information correctness).&lt;/p&gt;

&lt;p&gt;Niu, could you please have a look at this one?&lt;/p&gt;</comment>
                            <comment id="46129" author="niu" created="Mon, 8 Oct 2012 05:34:48 +0000"  >&lt;p&gt;I can reproduce it by &quot;NOFORMAT=1 sh llmount.sh; ONLY=17m sh sanity.sh&quot; or running the 17m twice &quot;ONLY=17m sh sanity.sh; ONLY=17m sh sanity.sh&quot;, but seems OSTs doesn&apos;t have such problem, so it&apos;s unlikely a kernel or e2fsprogs bug.&lt;/p&gt;

&lt;p&gt;I think it because we missed ll_vfs_dq_init() for some system objects, like llog, oi, last_rcvd, etc. so the block accounting for those existing objects is missed. (if they are newly created, then there isn&apos;t any problem), I&apos;ll post a patch to fix it soon.&lt;/p&gt;</comment>
                            <comment id="46131" author="niu" created="Mon, 8 Oct 2012 06:00:22 +0000"  >&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/4220&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/4220&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="46228" author="adilger" created="Mon, 8 Oct 2012 23:19:30 +0000"  >&lt;p&gt;Patch is merged, just after the 2.3.53 tag. &lt;/p&gt;</comment>
                            <comment id="46484" author="adilger" created="Fri, 12 Oct 2012 15:37:26 +0000"  >&lt;p&gt;Was this patch actually tested to fix the problem?  I still see the same issue here (running mmp.sh test 8 in this case):&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;e2fsck 1.42.5.wc3 (15-Sep-2012)
Starting mds1:   /dev/vg_sookie/lvmdt1 /mnt/mds1
Start of /dev/vg_sookie/lvmdt1 on mds1 failed 1
[QUOTA WARNING] Usage inconsistent for ID 0:actual (1294336, 283) != expected (1253376, 279)
[QUOTA WARNING] Usage inconsistent for ID 0:actual (1294336, 283) != expected (1253376, 279)
:
:
[problems from LU-1861]
:
:
Update quota info for quota type 0? yes

Update quota info for quota type 1? yes
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Filesystem had previously been running other acceptance small tests, but I believe this hits early enough and consistently in sanity.sh that it is easily reproduced.&lt;/p&gt;</comment>
                            <comment id="46541" author="niu" created="Mon, 15 Oct 2012 00:14:21 +0000"  >&lt;p&gt;I verified the test fixed the problem of:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;NOFORMAT=1 sh llmount.sh; ONLY=17m sh sanity.sh (accounting for llog objects created during mount)&lt;/li&gt;
	&lt;li&gt;ONLY=17m sh sanity.sh; ONLY=17m sh sanity.sh (accounting for oi)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Maybe there is till something missed, I&apos;m checking into this. Thank you, Andreas.&lt;/p&gt;</comment>
                            <comment id="46554" author="niu" created="Mon, 15 Oct 2012 05:11:42 +0000"  >&lt;p&gt;more ll_vfs_dq_init() are added: &lt;a href=&quot;http://review.whamcloud.com/427&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/427&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Without above patch, I can reproduce the problem by &quot;sh sanity.sh; ONLY=8 sh mmp.sh&quot;.&lt;/p&gt;</comment>
                            <comment id="47000" author="niu" created="Mon, 29 Oct 2012 05:45:30 +0000"  >&lt;p&gt;patches landed for 2.4&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="17256">LU-2663</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|hzv58f:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4381</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>