While archiving a 5GiB file on a client:
I repeatedly checked the progress with lfs hsm_action:
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.