[LU-9255] lfs hsm_remove results in "Cannot send HSM request...Operation not permitted"

• Status: Closed
• Project: Lustre
• Type: Question/Request
• Priority: Minor
• Reporter: Michael Gilbert
• Assignee: WC Triage
• Resolution: Not a Bug

Description

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.

I don't have an actual "hsm" system, so I'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't work. For example:

[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 /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
 nfsd on /proc/fs/nfsd type nfsd (rw)
 172.16.2.1:/slurm_state/ on /var/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]# 

This output is all I get. There is no information in any of the lustre logs regarding what is happening. Can anyone help me?

Comments

[John Hammond]

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.

[Michael Gilbert]

Thank you so much for your response! Wow...I did not know that about the remove command. After reading the Lustre documentation, it wasn'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?

What I'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'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. 

Is this something that is possible to do?

[Michael Gilbert]

I also found this issue: LU-6494. 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?

[Quentin Bouget]

Am I right assuming that this is the same issue reported here? 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's back)

[John Hammond]

> I also found this issue: LU-6494. 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?

No. LU-6494 is about removing archived copies of files that have been deleted from Lustre.

> Am I right assuming that this is the same issue reported here?

Yes.