[LU-8452] unable to re-archive an "lost" file

• Status: Open
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Robert Read (Inactive)
• Assignee: WC Triage
• Resolution: Unresolved
• Severity: 3

Description

An HSM user reported that when an archived (and not released) file has been marked as "lost", then new attempts to archive the file are ignored. I think in this case it would make sense to treat the "lost" flag the same as "dirty" and allow a new archive request be used to archive the file again and clear the lost flag.

There are 3 options I can think to workaround this:

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.

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

{quote] # lfs hsm_set --norelease <lost_file> # lfs hsm_clear --lost <lost_file> {quote}

Once the new archive is completed you'll need to clear the norelease flag.

3. A third option would be to mark the file "dirty" by writing a portion of the file back to itself. This would also prevent the file being released, but won't need any flags to be changed once the file is archived again.

Comments

[Andreas Dilger]

Any preferences on which option you'd prefer more?

[Robert Read (Inactive)]

My preference is to have this fixed so it is possible to archive a lost file with needing any of the workarounds I suggested.