<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:17:39 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-8452] unable to re-archive an &quot;lost&quot; file</title>
                <link>https://jira.whamcloud.com/browse/LU-8452</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;An HSM user reported that when an archived (and not released) file has been marked as &quot;lost&quot;, then new attempts to archive the file are ignored. I think in this case it would make sense to treat the &quot;lost&quot; flag the same as &quot;dirty&quot; and allow a new archive request be used to archive the file again and clear the lost flag. &lt;/p&gt;

&lt;p&gt;There are 3 options I can think to workaround this:&lt;/p&gt;

&lt;p&gt;1. Use hsm_remove to clear the archive flag. This will prevent the file from being released and clears the lost flag so file can be re-archived.&lt;/p&gt;

&lt;p&gt;2. If the original copytool is not available (perhaps this is why lost was set in first place), then hsm_remove won&apos;t work. Another option is to set the norelease flag and then clear the lost flag.&lt;/p&gt;

{quote] 
 # lfs hsm_set --norelease &amp;lt;lost_file&amp;gt;
 # lfs hsm_clear --lost &amp;lt;lost_file&amp;gt;
{quote}

&lt;p&gt;Once the new archive  is completed you&apos;ll need to clear the norelease flag. &lt;/p&gt;

&lt;p&gt;3. A third option would be to mark the file &quot;dirty&quot; by writing a portion of the file back to itself. This would also prevent the file being released, but won&apos;t need any flags to be changed once the file is archived again. &lt;/p&gt;</description>
                <environment></environment>
        <key id="38509">LU-8452</key>
            <summary>unable to re-archive an &quot;lost&quot; file</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="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="rread">Robert Read</reporter>
                        <labels>
                    </labels>
                <created>Sat, 30 Jul 2016 13:47:45 +0000</created>
                <updated>Mon, 15 Aug 2016 18:54:05 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="160383" author="adilger" created="Sun, 31 Jul 2016 03:21:50 +0000"  >&lt;p&gt;Any preferences on which option you&apos;d prefer more?&lt;/p&gt;</comment>
                            <comment id="161920" author="rread" created="Mon, 15 Aug 2016 18:54:05 +0000"  >&lt;p&gt;My preference is to have this fixed so it is possible to archive a lost file with needing any of the workarounds I suggested.&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|hzyj13:</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>
                                                                                            <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>