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

Ubuntu 26.04 sanity-sec test_54 hung or crash

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • Lustre 2.18.0
    • Ubuntu 26.04
    • 3
    • 9223372036854775807

      This issue was created by maloo for jianyu <yujian@whamcloud.com>

      This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/148b1c9f-9e80-47ae-81a2-f58ee48bee6a

      test_54 failed with the following error:

      running as uid/gid/euid/egid 500/500/500/500, groups: 500
       [fscrypt] [unlock] [--verbose] [/mnt/lustre]
      2026/06/11 01:53:32 Reading config from "/etc/fscrypt.conf"
      2026/06/11 01:53:32 creating context for user "sanityusr"
      2026/06/11 01:53:32 /mnt/lustre is on lustre filesystem "/mnt/lustre" ()
      2026/06/11 01:53:32 performing sanity checks
      2026/06/11 01:53:32 found policy 7a7f89ac4a8b8a72edb91146356e6bf3 for "/mnt/lustre"
      2026/06/11 01:53:32 successfully read metadata from "/mnt/lustre/.fscrypt/policies/7a7f89ac4a8b8a72edb91146356e6bf3"
      2026/06/11 01:53:32 found data for policy 7a7f89ac4a8b8a72edb91146356e6bf3 on "/mnt/lustre"
      2026/06/11 01:53:32 data from filesystem and path agree
      2026/06/11 01:53:32 Detected support for filesystem keyring
      2026/06/11 01:53:32 FS_IOC_GET_ENCRYPTION_KEY_STATUS("/mnt/lustre", 7a7f89ac4a8b8a72edb91146356e6bf3) = errno 0, status=1, status_flags=0x0
      2026/06/11 01:53:32 successfully read metadata from "/mnt/lustre/.fscrypt/protectors/eade4efba8f3248e"
      2026/06/11 01:53:32 optionFn(7a7f89ac4a8b8a72edb91146356e6bf3)
      2026/06/11 01:53:32 selecting from 1 protector
      2026/06/11 01:53:32 protector eade4efba8f3248e selected in callback
      2026/06/11 01:53:32 KeyFunc(custom protector "protector", false)
      Enter custom passphrase for protector "protector": 2026/06/11 01:53:32 running passphrase hash for protector eade4efba8f3248e
      2026/06/11 01:53:33 valid wrapping key for protector eade4efba8f3248e
      2026/06/11 01:53:33 unwrapping policy 7a7f89ac4a8b8a72edb91146356e6bf3 with protector
      2026/06/11 01:53:33 FS_IOC_ADD_ENCRYPTION_KEY("/mnt/lustre", 7a7f89ac4a8b8a72edb91146356e6bf3, ) = errno 0
      "/mnt/lustre" is now unlocked and ready for use.
      /mnt/lustre:
      total 12
      drwx------+2 sanityusr sanityusr 4096 Jun 11 01:53 .
      drwxr-xr-x 7 root      root      4096 Jun 11 00:24 ..
      -rw-r--r--+1 sanityusr sanityusr 4096 Jun 11 01:53 encfile
      10.240.28.83@tcp:/lustre/d54.sanity-sec/vault /mnt/lustre lustre rw,flock,checksum,encrypt,lazystatfs,lruresize,nolock,statfs_project,nouser_fid2path,user_xattr,verbose 0 0
      CMD: onyx-156vm10.onyx.whamcloud.com grep -c /mnt/lustre' ' /proc/mounts
      Stopping client onyx-156vm10.onyx.whamcloud.com /mnt/lustre (opts:)
      CMD: onyx-156vm10.onyx.whamcloud.com lsof -t /mnt/lustre
      

      Test session details:
      clients: https://build.whamcloud.com/job/lustre-reviews/126285 - 7.0.0-22-generic
      servers: https://build.whamcloud.com/job/lustre-reviews/126285 - 4.18.0-553.125.1.el8_lustre.x86_64

      <<Please provide additional information about the failure here>>

      VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
      sanity-sec test_54 - Timeout occurred after 535 minutes, last suite running was sanity-sec

            sebastien Sebastien Buisson
            maloo Maloo
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: