<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:24:34 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-9255] lfs hsm_remove results in &quot;Cannot send HSM request...Operation not permitted&quot;</title>
                <link>https://jira.whamcloud.com/browse/LU-9255</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I am running Lustre 2.8 and am trying to get hsm to work properly. The archive, release, and restore commands seem to work fine, but the remove command results in a failure.&lt;/p&gt;

&lt;p&gt;I don&apos;t have an actual &quot;hsm&quot; system, so I&apos;m trying to use a local directory simply called `/hsm`. The lhsmtool_posix tool works great for archiving and restoring the data, but for some reason the remove function doesn&apos;t work. For example:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;[root@head ricky]# mount
 /dev/mapper/vg_head-lv_root on / type ext4 (rw)
 proc on /proc type proc (rw)
 sysfs on /sys type sysfs (rw)
 devpts on /dev/pts type devpts (rw,gid=5,mode=620)
 tmpfs on /dev/shm type tmpfs (rw)
 /dev/sda1 on /boot type ext4 (rw)
 /dev/mapper/vg_data-home on /home type xfs (rw)
 /dev/mapper/vg_data-common on /common type xfs (rw)
 /dev/mapper/vg_data-packages on /packages type xfs (rw)
 /dev/mapper/vg_data-scratch on /scratch type xfs (rw)
 /dev/mapper/vg_data-scratch--lt on /scratch-lt type xfs (rw)
 /dev/mapper/vg_data-slurm_state on /slurm_state type xfs (rw,noatime)
 none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
 sunrpc on /&lt;span class=&quot;code-keyword&quot;&gt;var&lt;/span&gt;/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
 nfsd on /proc/fs/nfsd type nfsd (rw)
 172.16.2.1:/slurm_state/ on /&lt;span class=&quot;code-keyword&quot;&gt;var&lt;/span&gt;/spool/slurm type nfs (rw,vers=4,addr=172.16.2.1,clientaddr=172.16.2.1)
 mds@tcp:/scratch on /lustre-scratch type lustre (rw)
 /dev/sdd1 on /hsm1 type ext4 (rw)
 [root@head ricky]# pwd
 /lustre-scratch/ricky
 [root@head ricky]# lfs hsm_state file
 file: (0x0000000d) released exists archived, archive_id:1
 [root@head ricky]# lfs hsm_remove file
 Cannot send HSM request (use of file): Operation not permitted
 [root@head ricky]# 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt; This output is all I get. There is no information in any of the lustre logs regarding what is happening. Can anyone help me?&lt;/p&gt;</description>
                <environment></environment>
        <key id="45012">LU-9255</key>
            <summary>lfs hsm_remove results in &quot;Cannot send HSM request...Operation not permitted&quot;</summary>
                <type id="9" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/undefined.png">Question/Request</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="6">Not a Bug</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="mkgilbert">Michael Gilbert</reporter>
                        <labels>
                    </labels>
                <created>Fri, 24 Mar 2017 20:06:15 +0000</created>
                <updated>Wed, 31 May 2017 13:40:02 +0000</updated>
                            <resolved>Wed, 31 May 2017 13:39:56 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="189623" author="jhammond" created="Fri, 24 Mar 2017 20:28:16 +0000"  >&lt;p&gt;HSM remove on a released file would result in data loss and is therefore prohibited. If the file is restored then HSM remove will be allowed.&lt;/p&gt;</comment>
                            <comment id="189629" author="mkgilbert" created="Fri, 24 Mar 2017 21:18:40 +0000"  >&lt;p&gt;Thank you so much for your response! Wow...I did not know that about the remove command. After reading the Lustre documentation, it wasn&apos;t clear to me that remove was only meant to allow deletion of copies of existing lustre files. So then there is no way to have the HSM act like a backup that gets purged independently of the Lustre file system?&lt;/p&gt;

&lt;p&gt;What I&apos;d really like to do is archive and release files from Lustre after 30 days of non-use and then only remove files from the archive that haven&apos;t been updated in 90 days. This would mean all files older than 90 days would be completely gone. The reason for this is our Lustre file system is being used as a scratch area, not permanent storage.&#160;&lt;/p&gt;

&lt;p&gt;Is this something that is possible to do?&lt;/p&gt;</comment>
                            <comment id="189633" author="mkgilbert" created="Fri, 24 Mar 2017 21:26:01 +0000"  >&lt;p&gt;I also found this issue: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-6494&quot; title=&quot;hsm: lfs cannot remove an archived file that has been deleted&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-6494&quot;&gt;&lt;del&gt;LU-6494&lt;/del&gt;&lt;/a&gt;. Based on this, it seems like I should still be able to remove released Lustre files from the archive if I pass in the fid. Am I understanding that correctly?&lt;/p&gt;</comment>
                            <comment id="197531" author="bougetq" created="Tue, 30 May 2017 08:07:57 +0000"  >&lt;p&gt;Am I right assuming that this is the same issue reported &lt;a href=&quot;https://github.com/cea-hpc/robinhood/issues/74&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;? Can it be closed? (just to be complete, the answer to your last question is: no, you cannot delete the data associated to a released file through Lustre, you can only do so by going behind Lustre&apos;s back)&lt;/p&gt;</comment>
                            <comment id="197671" author="jhammond" created="Wed, 31 May 2017 13:39:32 +0000"  >&lt;p&gt;&amp;gt; I also found this issue: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-6494&quot; title=&quot;hsm: lfs cannot remove an archived file that has been deleted&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-6494&quot;&gt;&lt;del&gt;LU-6494&lt;/del&gt;&lt;/a&gt;. Based on this, it seems like I should still be able to remove released Lustre files from the archive if I pass in the fid. Am I understanding that correctly?&lt;/p&gt;

&lt;p&gt;No. &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-6494&quot; title=&quot;hsm: lfs cannot remove an archived file that has been deleted&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-6494&quot;&gt;&lt;del&gt;LU-6494&lt;/del&gt;&lt;/a&gt; is about removing archived copies of files that have been deleted from Lustre.&lt;/p&gt;

&lt;p&gt;&amp;gt; Am I right assuming that this is the same issue reported here?&lt;/p&gt;

&lt;p&gt;Yes.&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|hzz89z:</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>