<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:40:36 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-146] Use of obdfilter_survey is cautioned against unnecessarily on production file systems</title>
                <link>https://jira.whamcloud.com/browse/LUDOC-146</link>
                <project id="10070" key="LUDOC">Lustre Documentation</project>
                    <description>&lt;p&gt;The Operations Manual contains the following warning:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The obdfilter_survey script is destructive and should not be run on devices that containing existing data that needs to be preserved. Thus, tests using obdfilter_survey should be run before the Lustre file system is placed in production.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;However, the tool &lt;em&gt;can&lt;/em&gt; be used in a production environment so long as it isn&apos;t used in &apos;manual&apos; mode.&lt;/p&gt;

&lt;p&gt;Further, due to the indentation, it isn&apos;t clear if this warning and the other notes pertain to the &apos;Remote file system over the network&apos; section, or for the tool in general.&lt;/p&gt;

&lt;p&gt;The same clarification should be made to README.obdfilter-survey in the lustre-iokit.&lt;/p&gt;</description>
                <environment></environment>
        <key id="18749">LUDOC-146</key>
            <summary>Use of obdfilter_survey is cautioned against unnecessarily on production file systems</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="1">Fixed</resolution>
                                        <assignee username="rhenwood">Richard Henwood</assignee>
                                    <reporter username="spitzcor">Cory Spitz</reporter>
                        <labels>
                            <label>QContent</label>
                    </labels>
                <created>Wed, 8 May 2013 14:27:21 +0000</created>
                <updated>Mon, 24 Jun 2013 20:21:16 +0000</updated>
                            <resolved>Mon, 24 Jun 2013 20:21:12 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="59028" author="spitzcor" created="Wed, 22 May 2013 02:32:15 +0000"  >&lt;p&gt;Whether obdfilter_survey was safe for use on a production file system was discussed on HPDD-discuss/lustre-discuss where Andreas replied:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;On 2013/21/03 4:09 AM, &quot;Michael Kluge&quot; &amp;lt;Michael.Kluge@tu-dresden.de&amp;gt; wrote:&lt;br/&gt;
I have read through the documentation for obdfilter-survey but could not&lt;br/&gt;
found any information on how invasive the test is. Will it destroy an&lt;br/&gt;
already formatted OST or render user data unusable?&lt;/p&gt;

&lt;p&gt;It shouldn&apos;t - the obdfilter-survey uses a different object sequence (2)&lt;br/&gt;
compared to normal filesystem objects (currently always 0), so the two do&lt;br/&gt;
not collide.&lt;/p&gt;

&lt;p&gt;Cheers, Andreas&lt;/p&gt;&lt;/blockquote&gt;</comment>
                            <comment id="59168" author="spitzcor" created="Thu, 23 May 2013 15:22:28 +0000"  >&lt;p&gt;benchmark: water-down obdfilter-survey warning.&lt;br/&gt;
&lt;a href=&quot;http://review.whamcloud.com/6416&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/6416&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="59979" author="rhenwood" created="Tue, 4 Jun 2013 17:16:03 +0000"  >&lt;p&gt;Cory, can you cast judgement on the patch:  &lt;a href=&quot;http://review.whamcloud.com/6416&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/6416&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="59988" author="spitzcor" created="Tue, 4 Jun 2013 18:11:05 +0000"  >&lt;p&gt;I just gave it +1.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                    <customfield id="customfield_10003" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Business Value</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>15.26</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <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|hzvqf3:</customfieldvalue>

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