<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:32:45 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-10177] DoM: manual migration MDT-OST</title>
                <link>https://jira.whamcloud.com/browse/LU-10177</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Make migration for DoM files with LFS command. This is not working out-of-box for Data-on-MDT files because it is not enough just change layout, data should be moved as well.&lt;/p&gt;</description>
                <environment></environment>
        <key id="42343">LU-10177</key>
            <summary>DoM: manual migration MDT-OST</summary>
                <type id="7" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/task_agile.png">Technical task</type>
                            <parent id="49050">LU-10176</parent>
                                    <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</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="1">Fixed</resolution>
                                        <assignee username="tappro">Mikhail Pershin</assignee>
                                    <reporter username="tappro">Mikhail Pershin</reporter>
                        <labels>
                            <label>DoM2</label>
                    </labels>
                <created>Fri, 9 Dec 2016 09:26:39 +0000</created>
                <updated>Mon, 11 Feb 2019 17:38:44 +0000</updated>
                            <resolved>Sat, 6 Oct 2018 13:18:25 +0000</resolved>
                                                    <fixVersion>Lustre 2.12.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="179515" author="tappro" created="Wed, 4 Jan 2017 09:11:27 +0000"  >&lt;p&gt;1) MDT to OST migration&lt;br/&gt;
DOM layout + data on MDT -&amp;gt; OST layout + data on OST&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;create volatile file (OST new layout);&lt;/li&gt;
	&lt;li&gt;move data from DOM file to volatile file;&lt;/li&gt;
	&lt;li&gt;swap layout (old DOM inode + new layout on OST);&lt;/li&gt;
	&lt;li&gt;delete data on MDT by truncating local inode on MDT (*** new step). It is not trivial case too, need special code path.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;2) OST to MDT&lt;br/&gt;
OST layout + data on OSTs -&amp;gt; DOM layout + data on MDT&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;no sense to create volatile file, because its data will be tied to its new MDT inode, but we want to keep data with the old inode. We need to read data from OSTs stripes and write it to the inode blocks on MDT (like to the DOM file)&lt;/li&gt;
	&lt;li&gt;set DOM pattern to the original file&lt;/li&gt;
	&lt;li&gt;create volatile file with the same OST layout (replica)&lt;/li&gt;
	&lt;li&gt;copy data from it to the old file with DOM pattern&lt;/li&gt;
	&lt;li&gt;delete stripes from the original file layout&lt;/li&gt;
	&lt;li&gt;delete replica&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="214636" author="adilger" created="Sat, 25 Nov 2017 21:03:14 +0000"  >&lt;p&gt;This should be able to use the existing FLR code paths on the client to open the MDT and OST components of the file for read/write to write &lt;em&gt;under&lt;/em&gt; the other component.  For some time at least this would become an FLR mirrored file, which is desirable to allow in any case.  For FLR the DoM component would be preferred if the file size is below MDT size limit, and the OST component would be preferred if the file size is larger.&lt;/p&gt;</comment>
                            <comment id="231807" author="gerrit" created="Fri, 10 Aug 2018 16:46:51 +0000"  >&lt;p&gt;Mike Pershin (mpershin@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/32979&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/32979&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10177&quot; title=&quot;DoM: manual migration MDT-OST&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10177&quot;&gt;&lt;del&gt;LU-10177&lt;/del&gt;&lt;/a&gt; lfs: support DOM-to-OST migration&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: ce9af3080a1cc66eacb647940aa9b3502641c19c&lt;/p&gt;</comment>
                            <comment id="231831" author="adilger" created="Sat, 11 Aug 2018 07:30:47 +0000"  >&lt;p&gt;How much work will it be to be able to do the reverse - to be able to migrate small files to the MDT?  I&apos;m thinking that the FLR resync ioctl to open the MDT component to &quot;write behind&quot; the OST object and then just drop the OST component. &lt;/p&gt;</comment>
                            <comment id="231836" author="tappro" created="Sat, 11 Aug 2018 18:14:54 +0000"  >&lt;p&gt;well, my idea was to make that manually first with steps like:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;lfs mirror extend -N &amp;lt;new DOM layout&amp;gt; &amp;lt;some non-dom file&amp;gt;&lt;/li&gt;
	&lt;li&gt;lfs resync&lt;/li&gt;
	&lt;li&gt;lfs split --mirror-id 1 -d&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;and make it work, it is not working just out of box and requires code update to make DOM code understand FLR cases, e.g. DOM component can be not first one with FLR, but still should be first one inside a mirror, also we need to allow only one DOM component in all mirrors and so on.&lt;br/&gt;
I think that will be good as first step, at least simple script will be able to migrate files to MDT like that and Lustre code will be ready for FLR+DOM configurations. I&apos;d say it shouldn&apos;t take a lot of time, but let me do more checks first.&lt;/p&gt;

&lt;p&gt;Next step will be implementing that in code as single call, probably with some optimizations.&lt;/p&gt;</comment>
                            <comment id="234463" author="gerrit" created="Fri, 5 Oct 2018 22:25:53 +0000"  >&lt;p&gt;Oleg Drokin (green@whamcloud.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/32979/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/32979/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-10177&quot; title=&quot;DoM: manual migration MDT-OST&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-10177&quot;&gt;&lt;del&gt;LU-10177&lt;/del&gt;&lt;/a&gt; lfs: support DOM-to-OST migration&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: f651470c13f83bc11237e12f6fdce9cdbf96561b&lt;/p&gt;</comment>
                            <comment id="234523" author="pjones" created="Sat, 6 Oct 2018 13:18:25 +0000"  >&lt;p&gt;Landed for 2.12&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10324">
                    <name>Cloners</name>
                                                                <inwardlinks description="is cloned by">
                                        <issuelink>
            <issuekey id="53400">LU-11421</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="53581">LU-11508</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="18725">LU-3285</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="49376">LU-10258</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="51798">LU-10910</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_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzyy1z:</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>