<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:03:23 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-13691] Allow for lfs migrate between MDTs to include DOM</title>
                <link>https://jira.whamcloud.com/browse/LU-13691</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Would it be possible to add options to allow lfs migrate to be used for migration of files/directories between MDTs to include DOM data partitions?&#160; For example directoryA has files with inodes and a DOM layout on MDT00.&#160; Lfs migrate directoryA to MDT01 such that both inodes and DOM components are migrated.&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Would it be possible to have data beyond the MDT remain in place on OSTs?&#160;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="59618">LU-13691</key>
            <summary>Allow for lfs migrate between MDTs to include DOM</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="laisiyao">Lai Siyao</assignee>
                                    <reporter username="klamb">Kyle Lamb</reporter>
                        <labels>
                    </labels>
                <created>Wed, 17 Jun 2020 17:18:54 +0000</created>
                <updated>Fri, 6 Jan 2023 20:10:28 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="273341" author="adilger" created="Fri, 19 Jun 2020 17:51:45 +0000"  >&lt;p&gt;Mike, and Lai, could you please provide some input on how easy or hard this would be to implement.&lt;/p&gt;

&lt;p&gt;This is similar to DNE directory migration, but would also move the DoM data. I believe that it is possible to create FLR mirrors of DoM files today, but this keeps the same inode on the MDT.  AFAIK, it is &lt;b&gt;not&lt;/b&gt; possible to migrate the inode with DoM  to a different MDT at the same time, but maybe that was implemented in 2.14?&lt;/p&gt;</comment>
                            <comment id="273428" author="laisiyao" created="Mon, 22 Jun 2020 02:26:02 +0000"  >&lt;p&gt;In the last patch of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11025&quot; title=&quot;DNE3: directory restripe&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11025&quot;&gt;&lt;del&gt;LU-11025&lt;/del&gt;&lt;/a&gt;, if it&apos;s DoM file, migration will migrate dirent, and leave inode untouched, instead of return -EOPNOTSUPP.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="58191">LU-13298</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="52253">LU-11025</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                                        </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_10030" key="com.atlassian.jira.plugin.system.customfieldtypes:labels">
                        <customfieldname>Epic/Theme</customfieldname>
                        <customfieldvalues>
                                        <label>dne</label>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i0131b:</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>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>