<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:43: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-4487] LFSCK 5: modify Lustre with backend mounted directly and keep system consistency</title>
                <link>https://jira.whamcloud.com/browse/LU-4487</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;There are some remaining issues for the following patch to be further discussed and resolved:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/#/c/8002/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/8002/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In fact, there are some rude usages for Lustre admin to modify Lustre with ldiskfs mounted directly, which may cause some stale OI mapping entries left in the OI files but related inodes have been removed. Sometimes, such modification are meaningful. For example: removing last_rcvd file to resolve some recovery trouble; removing OI files to increase OI files count for larger scale or shrink OI files unused space; and so on. On the other hand, such modification brings trouble to the system consistency. Currently, we use OI scrub to resolve those trouble as much as possible. But is seems not the best solution. Maybe we can introduce more suitable way to resolve the issues in the future. For example, we can offer a offline tools set to admin to modify Lustre files and related OI mappings together, then guarantee that even though the modification is done under ldiskfs mounted, the system is still is consistent.&lt;/p&gt;</description>
                <environment></environment>
        <key id="22744">LU-4487</key>
            <summary>LFSCK 5: modify Lustre with backend mounted directly and keep system consistency</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="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="yong.fan">nasf</assignee>
                                    <reporter username="yong.fan">nasf</reporter>
                        <labels>
                    </labels>
                <created>Wed, 15 Jan 2014 03:34:15 +0000</created>
                <updated>Sun, 30 Jan 2022 10:53:11 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="105053" author="yong.fan" created="Thu, 29 Jan 2015 00:25:20 +0000"  >&lt;p&gt;We will allow the admin to directly modify the ldiskfs backend under some special cases, and make the normal RPC services to remove the unused OI mappings during the OI lookup.&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|hzwcuv:</customfieldvalue>

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