[LU-5231] HSM: incorrect progress reported by lfs hsm_action

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.6.0
• Labels: HSM patch
• Environment: Centos 6.5; Lustre 2.5.56
• Severity: 3
• Assignee: WC Triage
• Reporter: Frank Zago (Inactive)

Description

While archiving a 5GiB file on a client:

# ls -l bigf
-rw-r--r--  1 root root 5129887744 Jun 18 16:48 bigf
# lfs hsm_archive bigf

I repeatedly checked the progress with lfs hsm_action:

bigf: ARCHIVE running (0xa00000 bytes moved)
...
bigf: ARCHIVE running (0x3200000 bytes moved)
...
bigf: ARCHIVE running (0x6400000 bytes moved)
...
...
...
bigf: ARCHIVE running (0x1a0e500000 bytes moved)
...
bigf: NOOP

The last result should have been close to 5 GiB, instead it was 0x1a0e500000 = 111909273600 = 104GiB

It appears the (correct) lengths sent by the copytool through llapi_hsm_action_progress() are being added somewhere in the kernel modules.

Also, is there a reason for the reported size to be written in hex? It's not convenient.