<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:37:18 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-3833] HSM POSIX copytool sparse file handling</title>
                <link>https://jira.whamcloud.com/browse/LU-3833</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;The copytool does not check for sparseness of files. Hence truncating a file to a very large size will create a potential DoS if that file is archived.&lt;/p&gt;</description>
                <environment></environment>
        <key id="20606">LU-3833</key>
            <summary>HSM POSIX copytool sparse file handling</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</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="wc-triage">WC Triage</assignee>
                                    <reporter username="jhammond">John Hammond</reporter>
                        <labels>
                            <label>HSM</label>
                    </labels>
                <created>Fri, 23 Aug 2013 20:51:29 +0000</created>
                <updated>Wed, 26 Jan 2022 19:40:42 +0000</updated>
                                            <version>Lustre 2.5.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="69860" author="adilger" created="Thu, 24 Oct 2013 23:09:47 +0000"  >&lt;p&gt;This could probably be avoided to some extent by having the policy engine make decisions based on the number of allocated blocks rather than using the size of the file.  It may also make sense for Robin Hood to allow specifying in the policy to avoid (or reduce) the priority for handling sparse files (possibly as a factor of the &quot;sparseness&quot;) if the archive does not handle sparse files well.  Otherwise, some file formats like HDF5 may have very large sparse address spaces that would fill both the archive and Lustre if handled poorly.&lt;/p&gt;

&lt;p&gt;A second-level enhancement would be to use FIEMAP to copy the file sparsely to/from the archive (assuming the archive itself has efficient sparse file handling).&lt;/p&gt;</comment>
                            <comment id="79099" author="bfaccini" created="Wed, 12 Mar 2014 09:15:29 +0000"  >&lt;p&gt;John, Andreas, sorry for the late update on this but since this looks more as an improvement/feature ...&lt;br/&gt;
So back to your proposals and ideas, I will try to work in both directions :&lt;/p&gt;

&lt;p&gt;          _ optimize (to be checked, with help from T.Leibovici, if still to be done?) RobinHood handling of sparse files, with associated Policy configuration parameters, to be based on blocks usage vs file-size.&lt;/p&gt;

&lt;p&gt;          _ enhance copytool to use FIEMAP if archive filesystem support it. BTW, I am not sure if the actual HSM-Restore feature already use FIEMAP based on original+released file layout?&lt;/p&gt;

&lt;p&gt;I will try to come up with some basic changes and may be more detailed thoughts soon now.&lt;/p&gt;

</comment>
                            <comment id="324060" author="adilger" created="Wed, 26 Jan 2022 19:37:43 +0000"  >&lt;p&gt;Mike Pershin (mpershin@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/40530&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/40530&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3833&quot; title=&quot;HSM POSIX copytool sparse file handling&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3833&quot;&gt;LU-3833&lt;/a&gt; hsm: lhsmtool to handle sparse files&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: ae180a1080dc1cb3990d8f53caee95e11a160248&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="58545">LU-13397</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="31079">LU-6848</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|hzvz6n:</customfieldvalue>

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