<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:44:10 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-11471] IO Errors during failover  with very few number of OSTs</title>
                <link>https://jira.whamcloud.com/browse/LU-11471</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;one of our customer is noticed IO errors during failover with fewer OST.  we would like to add a  note into the Best practice section or OST planning section &lt;br/&gt;
========================&lt;br/&gt;
During  Fail over situation with few OSTs possibly cause I/O errors on the client side. &lt;/p&gt;</description>
                <environment>Lustre 2.5.X &lt;br/&gt;
</environment>
        <key id="33847">LU-11471</key>
            <summary>IO Errors during failover  with very few number of OSTs</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="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="3">Duplicate</resolution>
                                        <assignee username="tappro">Mikhail Pershin</assignee>
                                    <reporter username="rganesan@ddn.com">Rajeshwaran Ganesan</reporter>
                        <labels>
                    </labels>
                <created>Thu, 24 Dec 2015 16:09:56 +0000</created>
                <updated>Sun, 16 Jan 2022 08:27:00 +0000</updated>
                            <resolved>Sun, 16 Jan 2022 08:27:00 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="137789" author="rganesan@ddn.com" created="Mon, 4 Jan 2016 13:04:32 +0000"  >&lt;p&gt;we would like add,  If the MDS has no currently active OSTs, create requests fail with an I/O error. And we will see the IO errors at the clients.&lt;/p&gt;</comment>
                            <comment id="166709" author="jgmitter" created="Wed, 21 Sep 2016 14:00:13 +0000"  >&lt;p&gt;Hi Rajeshwaran,&lt;/p&gt;

&lt;p&gt;Are you familiar with how to push such an update to the manual?&lt;/p&gt;

&lt;p&gt;For details on how to submit changes to the manual, please see:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;&lt;a href=&quot;https://wiki.hpdd.intel.com/display/PUB/Making+changes+to+the+Lustre+Manual&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://wiki.hpdd.intel.com/display/PUB/Making+changes+to+the+Lustre+Manual&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href=&quot;https://wiki.hpdd.intel.com/display/PUB/Code+Documentation+Guidelines&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://wiki.hpdd.intel.com/display/PUB/Code+Documentation+Guidelines&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="187949" author="adilger" created="Sat, 11 Mar 2017 10:03:10 +0000"  >&lt;p&gt;I wonder whether this should rather be considered a bug in the code, and the MDS should block file creations if all of the OSTs become unavailable after startup?&lt;/p&gt;</comment>
                            <comment id="207549" author="rganesan@ddn.com" created="Wed, 6 Sep 2017 08:20:39 +0000"  >&lt;p&gt;please close this case&lt;/p&gt;</comment>
                            <comment id="234372" author="adilger" created="Thu, 4 Oct 2018 17:02:56 +0000"  >&lt;p&gt;Reopening this issue. With the advent of Data-on-MDT we will at some point want to allow filesystems with only MDTs to be created. At that point, this check has to be removed. &lt;/p&gt;

&lt;p&gt;As a starting point, we could add a tunable that allows this behavior to be selected by the admin - return an error if no OSTs are available, or cause the client to block and wait for an OST to become available. I think in the case where an OST was previously available, but they are temporarily offline due to failover, the client should block. If the file being created has a DoM component at the start, then it should not block. &lt;/p&gt;</comment>
                            <comment id="322872" author="tappro" created="Sun, 16 Jan 2022 08:27:00 +0000"  >&lt;p&gt;Main ticket for remaining work is &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10995&quot; title=&quot;DoM2: allow MDT-only filesystems &quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10995&quot;&gt;LU-10995&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="52102">LU-10995</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_10490" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                        <customfieldname>End date</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 4 Jan 2016 16:09:56 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzxwrr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</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>
                                                                                                                        <customfield id="customfield_10493" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                        <customfieldname>Start date</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 24 Dec 2015 16:09:56 +0000</customfieldvalue>

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