<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:40:59 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>[LUDOC-193] Wide Striping feature flag is incorrect in documentation</title>
                <link>https://jira.whamcloud.com/browse/LUDOC-193</link>
                <project id="10070" key="LUDOC">Lustre Documentation</project>
                    <description>&lt;p&gt;Section 5.3.3, page 27 (of the PDF Manual) states that you need to use the tune2fs -O option for large_xattr &amp;#8211; when in fact it is ea_inode. Tune2fs -o large_xattr fails because it&apos;s an unknown option. I asked James Simmons and the mkfs.lustre option for large_xattr fails as well. We recently had to enable this on our Lustre 2.4 filesystem because we forgot to enable it at format time. &lt;/p&gt;</description>
                <environment></environment>
        <key id="21699">LUDOC-193</key>
            <summary>Wide Striping feature flag is incorrect in documentation</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="1">Fixed</resolution>
                                        <assignee username="jamesanunez">James Nunez</assignee>
                                    <reporter username="hilljjornl">Jason Hill</reporter>
                        <labels>
                    </labels>
                <created>Tue, 29 Oct 2013 12:57:22 +0000</created>
                <updated>Tue, 31 Dec 2013 18:24:17 +0000</updated>
                            <resolved>Tue, 31 Dec 2013 18:24:17 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="71649" author="jamesanunez" created="Fri, 15 Nov 2013 18:25:41 +0000"  >&lt;p&gt;Jason, &lt;/p&gt;

&lt;p&gt;There is room for confusion around the large_xattr/ea_inode feature. Right now, you can use &quot;large_xattr&quot; and &quot;ea_inode&quot; interchangeably in tune2fs and with mkfs.lustre, i.e. &quot;tune2fs -O large_xattr ...&quot; and &quot;tune2fs -O ea_inode&quot; produce the same result and the same is true for mkfs. In either case, you will see &quot;ea_inode&quot; in the filesystem features list with dumpe2fs. I just tested this with the latest 2.5.0 and 2.4.1. &lt;/p&gt;

&lt;p&gt;If your experience differs from what I&apos;ve said above, please let me know what version of the code you are seeing this in and I will look into it. &lt;/p&gt;

&lt;p&gt;I know that there is a possibility that only large_xattr will be used in the future, but that has not happened yet. Thus, I agree that the documentation should be updated. I will post a patch to the documentation later today.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
James&lt;/p&gt;

&lt;p&gt;EDIT: What I should have said is, if your experience differs from what I outlined above, please let me know the version of e2fsprogs you are using. I used version 1.42.7.wc1. &lt;/p&gt;</comment>
                            <comment id="71688" author="jamesanunez" created="Fri, 15 Nov 2013 21:35:52 +0000"  >&lt;p&gt;Proposed patch at: &lt;a href=&quot;http://review.whamcloud.com/#/c/8297/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/8297/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="74193" author="jamesanunez" created="Tue, 31 Dec 2013 18:24:17 +0000"  >&lt;p&gt;Landed in latest Lustre Documentation.&lt;/p&gt;</comment>
                    </comments>
                    <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|hzw767:</customfieldvalue>

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