Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-5231

HSM: incorrect progress reported by lfs hsm_action

    Details

    • Type: Bug
    • Status: Reopened
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: Lustre 2.6.0
    • Fix Version/s: None
    • Labels:
    • Environment:
      Centos 6.5
      Lustre 2.5.56
    • Severity:
      3
    • Rank (Obsolete):
      14572

      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.

        Attachments

          Activity

            People

            • Assignee:
              wc-triage WC Triage
              Reporter:
              fzago Frank Zago
            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated: