Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
3
-
9223372036854775807
Description
But when running lfs hsm_remove, one will notice that you cannot use FIDS:
#> lfs hsm_remove 0x200000401:0x1:0x0 Cannot stat 0x200000401:0x1:0x0: No such file or directory
Unless you use the --mntpath/-m option:
#> lfs hsm_remove --mntpath $MOUNT 0x200000401:0x1:0x0
The usage message of lfs hsm_remove:
usage: hsm_remove [--filelist FILELIST] [--data DATA] [--mntpath MOUNTPATH] [--archive NUM] <file|FID> ... Note: To remove files from the archive that have been deleted on Lustre, set mntpath and optionally archive. In that case, all the positional arguments and entries in the file list must be FIDs.
The note is about files that have been removed from Lustre.
I think a better usage message would be for example:
usage hsm_remove [--filelist FILELIST] [--data DATA] [--archive NUM] (FILE [FILE] | --mntpath MOUNTPATH FID [FID]) Note: one can remove data from the backend associated to deleted files in Lustre. To do so the --mntpath option is required and one has to use FIDS instead of file paths.
Attachments
Issue Links
- is related to
-
LU-9345 tests: sanity-hsm: test_29d: hsm_remove needs --mntpath for deleted files
- Resolved