<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:21:29 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-1997] &apos;exclude&apos; mount option does not work in lustre b2_1</title>
                <link>https://jira.whamcloud.com/browse/LU-1997</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;When mounting a lustre client, if we use the &apos;exclude&apos; option to ignore inactive OSTs this option is not well taken into account.&lt;/p&gt;

&lt;p&gt;From the mount.lustre manpage:&lt;/p&gt;

&lt;p&gt;exclude=ostlist              Start a client or MDT with a (colon-separated) list of known inactive OSTs.&lt;/p&gt;

&lt;p&gt;We run the mount command:&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@berlin105 ~&amp;#93;&lt;/span&gt;# mount -t lustre -o user_xattr,exclude=b8-OST0007 60.64.2.84@o2ib0,160.64.2.84@o2ib1:/b8 /b8&lt;/p&gt;

&lt;p&gt;In the dmesg we can see the option is seen by lustre:&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@berlin105 ~&amp;#93;&lt;/span&gt;# dmesg &lt;br/&gt;
Lustre: MGC60.64.2.84@o2ib: Reactivating import&lt;br/&gt;
Lustre: 18527:0:(obd_mount.c:1892:lustre_check_exclusion()) Excluding b8-OST0007 (on exclusion list)&lt;br/&gt;
Lustre: Mounted b8-client&lt;/p&gt;

&lt;p&gt;But the osc is always up and we can still write or read:&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@berlin105 ~&amp;#93;&lt;/span&gt;# lctl dl | grep b8-OST0007&lt;br/&gt;
 14 UP osc b8-OST0007-osc-ffff8808773f9c00 6dafd66d-9939-a1d6-cf40-529950167a65 5&lt;/p&gt;

&lt;p&gt;Whether the OST is disabled in the MDT or not the problem is always present and we are always accessing this OST from the client. If we try to deactivate the OST with &apos;lctl --device b8-OST0007-osc-ffff8808773f9c00 deactivate&apos; then the OST is well disabled but never when using exclude option.&lt;/p&gt;</description>
                <environment>rhel6.3</environment>
        <key id="16049">LU-1997</key>
            <summary>&apos;exclude&apos; mount option does not work in lustre b2_1</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="4">Incomplete</resolution>
                                        <assignee username="bogl">Bob Glossman</assignee>
                                    <reporter username="dmoreno">Diego Moreno</reporter>
                        <labels>
                    </labels>
                <created>Thu, 20 Sep 2012 11:45:40 +0000</created>
                <updated>Fri, 4 Mar 2016 18:45:03 +0000</updated>
                            <resolved>Fri, 4 Mar 2016 18:45:03 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="45394" author="pjones" created="Sat, 22 Sep 2012 08:48:35 +0000"  >&lt;p&gt;Bob&lt;/p&gt;

&lt;p&gt;Could you please look into this one?&lt;/p&gt;

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

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="45446" author="bogl" created="Mon, 24 Sep 2012 13:04:43 +0000"  >&lt;p&gt;This failure exists not just in 2.1 but in current master too.&lt;/p&gt;

&lt;p&gt;From an example debug log with +info and +config tracing a mount cmd with &apos;-o exclude=lustre-OST0001&apos;, it looks like the OST is getting set to inactive initially just like it should:&lt;/p&gt;


&lt;p&gt;00000100:00080000:0.0:1348503210.959470:0:27538:0:(pinger.c:425:ptlrpc_pinger_add_import()) adding pingable import 6f04d5c6-cdc4-18e4-1e30-9fc484f77a7f-&amp;gt;lustre-OST0001_UUID&lt;br/&gt;
00000020:00000040:0.0:1348503210.959472:0:27538:0:(genops.c:957:class_import_get()) import ffff880037e42800 refcount=4 obd=lustre-OST0001-osc-ffff88000f91f400&lt;br/&gt;
00020000:01000000:0.0:1348503210.959473:0:27538:0:(lov_obd.c:195:lov_connect_obd()) Connected tgt idx 1 lustre-OST0001_UUID (lustre-OST0001-osc-ffff88000f91f400) inactive&lt;/p&gt;

&lt;p&gt;but the effect of this is eliminated a short time later by a lov_set_osc_active():&lt;/p&gt;


&lt;p&gt;00000100:00080000:0.0:1348503210.960090:0:27013:0:(import.c:851:ptlrpc_connect_interpret()) connected to replayable target: lustre-OST0001_UUID&lt;br/&gt;
00000100:00080000:0.0:1348503210.960091:0:27013:0:(import.c:871:ptlrpc_connect_interpret()) ffff880037e42800 lustre-OST0001_UUID: changing import state from CONNECTING to FULL&lt;br/&gt;
00020000:00000040:0.0:1348503210.960092:0:27013:0:(lov_obd.c:392:lov_set_osc_active()) Searching in lov ffff880005a3a758 for uuid lustre-OST0001_UUID event(2)&lt;br/&gt;
00020000:00000040:0.0:1348503210.960092:0:27013:0:(lov_obd.c:402:lov_set_osc_active()) lov idx 0 is lustre-OST0000_UUID conn 0x3bc31bbe07ddca6f&lt;br/&gt;
00020000:00000040:0.0:1348503210.960093:0:27013:0:(lov_obd.c:402:lov_set_osc_active()) lov idx 1 is lustre-OST0001_UUID conn 0x3bc31bbe07ddca76&lt;br/&gt;
00020000:01000000:0.0:1348503210.960094:0:27013:0:(lov_obd.c:431:lov_set_osc_active()) Marking OSC lustre-OST0001_UUID active&lt;/p&gt;


&lt;p&gt;I&apos;m not sure why the inactive state doesn&apos;t persist.&lt;/p&gt;</comment>
                            <comment id="144665" author="jfc" created="Fri, 4 Mar 2016 18:45:03 +0000"  >&lt;p&gt;We are marking this as resolved, since b2_1 is no longer active.&lt;/p&gt;

&lt;p&gt;~ jfc.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="16387">LU-2200</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|hzvsmn:</customfieldvalue>

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