<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:35:57 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-3675] Support for linux 3.10 kernel</title>
                <link>https://jira.whamcloud.com/browse/LU-3675</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Tracker for 3.10 kernel support&lt;/p&gt;</description>
                <environment></environment>
        <key id="20128">LU-3675</key>
            <summary>Support for linux 3.10 kernel</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</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="laisiyao">Lai Siyao</assignee>
                                    <reporter username="simmonsja">James A Simmons</reporter>
                        <labels>
                    </labels>
                <created>Wed, 31 Jul 2013 16:12:04 +0000</created>
                <updated>Mon, 2 Dec 2013 13:48:25 +0000</updated>
                            <resolved>Mon, 2 Dec 2013 13:48:25 +0000</resolved>
                                    <version>Lustre 2.5.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="63441" author="pjones" created="Thu, 1 Aug 2013 05:36:12 +0000"  >&lt;p&gt;Lai&lt;/p&gt;

&lt;p&gt;You have been looking at some of these patches already&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="63493" author="simmonsja" created="Thu, 1 Aug 2013 19:12:05 +0000"  >&lt;p&gt;Patch &lt;a href=&quot;http://review.whamcloud.com/#/c/5390&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/5390&lt;/a&gt; from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2800&quot; title=&quot;build: clean out old autoconf options&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2800&quot;&gt;&lt;del&gt;LU-2800&lt;/del&gt;&lt;/a&gt; handles a block device function change now for 3.10 for lloop.c.&lt;/p&gt;</comment>
                            <comment id="69938" author="bogl" created="Fri, 25 Oct 2013 17:44:58 +0000"  >&lt;p&gt;I&apos;ve noticed an odd failure to autoload kernel modules on 3.10 kernels.  I thought this might be related to the CONFIG_MODULE_FORCE_LOAD setting in the kernel config, but setting that on or off seems to make no difference.  Causes a command like &apos;mount -t lustre ...&apos; client mount to fail due to lustre modules not getting loaded.&lt;/p&gt;

&lt;p&gt;In the short term for test purposes this isn&apos;t a big problem.  Just need to do a manual &apos;modprobe lustre&apos; before trying to do any client mounts.  Longer term really need to find the cause &amp;amp; a solution.&lt;/p&gt;</comment>
                            <comment id="70377" author="simmonsja" created="Thu, 31 Oct 2013 15:15:40 +0000"  >&lt;p&gt;With the patches from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3319&quot; title=&quot;Adapt to 3.10 upstream kernel proc_dir_entry change&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3319&quot;&gt;&lt;del&gt;LU-3319&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;http://review.whamcloud.com/#/c/5380&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/5380&lt;/a&gt; from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2800&quot; title=&quot;build: clean out old autoconf options&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2800&quot;&gt;&lt;del&gt;LU-2800&lt;/del&gt;&lt;/a&gt; I just mounted a ZFS server file system.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@spoon46 tests&amp;#93;&lt;/span&gt;# df &lt;br/&gt;
Filesystem           1K-blocks      Used Available Use% Mounted on&lt;br/&gt;
unionfs               88763392  61317120  22938624  73% /&lt;br/&gt;
none                       100         0       100   0% /dev/shm&lt;br/&gt;
none                   2957192     25312   2931880   1% /tmp&lt;br/&gt;
nccsfiler3.ccs.ornl.gov:/vol/techint&lt;br/&gt;
                     1015021568 871888352 143133216  86% /autofs/na3_techint&lt;br/&gt;
172.30.248.91:/data/shared-root-homedir&lt;br/&gt;
                      57799680  34323456  20540416  63% /root&lt;br/&gt;
172.30.248.91:/chexport&lt;br/&gt;
                      46445568  32187392  11898880  74% /chexport&lt;br/&gt;
lustre-mdt1/mdt1        157440      3072    152320   2% /tmp/lustre/mds1&lt;br/&gt;
lustre-ost1/ost1        157440      1152    154240   1% /tmp/lustre/ost1&lt;br/&gt;
lustre-ost2/ost2        157440      1152    154240   1% /tmp/lustre/ost2&lt;br/&gt;
172.30.248.48@tcp0:/lustre&lt;br/&gt;
                        314880      2304    308480   1% /lustre/barry&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@spoon46 tests&amp;#93;&lt;/span&gt;# uname -r&lt;br/&gt;
3.10.2&lt;/p&gt;</comment>
                            <comment id="70380" author="bogl" created="Thu, 31 Oct 2013 15:25:39 +0000"  >&lt;p&gt;James, excellent.  I have also done some successful zfs only server builds recently, but haven&apos;t done any functional testing yet.&lt;/p&gt;

&lt;p&gt;Any ETA on the few remaining osd-ldiskfs/osd_handler.c build blocking issues?&lt;/p&gt;</comment>
                            <comment id="70397" author="simmonsja" created="Thu, 31 Oct 2013 16:46:24 +0000"  >&lt;p&gt;I have the proc seq_file coding done for osd-ldiskfs but their is a lbug dealing with the osp layer when I attempt to mount a OST. I haven&apos;t updated the filldir_t changes for osd-ldisk yet. Even with those issues fixed their are problems building osd-ldiskfs with the fc19 ldiskfs patch Yeng had provided. I say it could be ready by the end of next week.&lt;/p&gt;</comment>
                            <comment id="70404" author="bogl" created="Thu, 31 Oct 2013 17:04:27 +0000"  >&lt;p&gt;some additional fixes to osd-ldiskfs just today.  see comments in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3373&quot; title=&quot;ldiskfs patches for FC19&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3373&quot;&gt;&lt;del&gt;LU-3373&lt;/del&gt;&lt;/a&gt;.  don&apos;t know if those address some of your issues or not.&lt;/p&gt;

&lt;p&gt;As far as I know the seq_file and readdir changes are still needed.  Looking forward to seeing those.  The end of next week sounds good to me.  Wasn&apos;t looking for a cast in concrete promise, just some idea of when.  Your answer is fine.&lt;/p&gt;</comment>
                            <comment id="70483" author="simmonsja" created="Fri, 1 Nov 2013 15:31:13 +0000"  >&lt;p&gt;Yep the patch &lt;a href=&quot;http://review.whamcloud.com/#/c/8116&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/8116&lt;/a&gt; from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3373&quot; title=&quot;ldiskfs patches for FC19&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3373&quot;&gt;&lt;del&gt;LU-3373&lt;/del&gt;&lt;/a&gt; did the trick. I have something that can build but does it work is another question.&lt;/p&gt;</comment>
                            <comment id="72579" author="simmonsja" created="Mon, 2 Dec 2013 13:09:34 +0000"  >&lt;p&gt;The patch from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2800&quot; title=&quot;build: clean out old autoconf options&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2800&quot;&gt;&lt;del&gt;LU-2800&lt;/del&gt;&lt;/a&gt; needed to support 3.10 kernels has been landed. Now only patches from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3319&quot; title=&quot;Adapt to 3.10 upstream kernel proc_dir_entry change&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3319&quot;&gt;&lt;del&gt;LU-3319&lt;/del&gt;&lt;/a&gt; are needed. We can close this ticket and focus on 3.11 kernel support now.&lt;/p&gt;</comment>
                            <comment id="72583" author="pjones" created="Mon, 2 Dec 2013 13:48:25 +0000"  >&lt;p&gt;ok. Thanks James&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="18888">LU-3319</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="19084">LU-3373</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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|hzvwwf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9489</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>