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

sanity test_27M: "stripe count , should be 8 for append"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for Andreas Dilger <adilger@whamcloud.com>

      This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/01323587-3a6c-4307-8adc-27c3a5d505a4

      test_27M failed with the following error:

      CMD: trevis-99vm4,trevis-99vm5 /usr/sbin/lctl set_param mdd.*.append_stripe_count=-1
      mdd.lustre-MDT0000.append_stripe_count=-1
      mdd.lustre-MDT0002.append_stripe_count=-1
      mdd.lustre-MDT0001.append_stripe_count=-1
      mdd.lustre-MDT0003.append_stripe_count=-1
      /usr/lib64/lustre/tests/sanity.sh: line 3027: /mnt/lustre/d27M.sanity/f27M.sanity.5: Invalid argument
      error: getstripe failed for /mnt/lustre/d27M.sanity/f27M.sanity.5.
      /usr/lib64/lustre/tests/sanity.sh: line 3029: [: -eq: unary operator expected
       sanity test_27M: @@@@@@ FAIL: (5) stripe count , should be 8 for append 
      

      At first glance this looks like a bug in the script where the stripe_count of -1 is causing a parsing error, but looking at the debug log it seems that the creation of f27M.sanity.5 failed. There are no messages on the console of the client or either MDS.

      The test first failed this way on 2022-08-09 on a patch that was landed on 2022-08-31, but there was a similar failure on 2022-08-18, so it is unlikely the original failure was caused by that patch.

      The client showed an -22 = -EINVAL error returned from the MDS for the create:

      00000080:00200000:1.0:1662583867.631802:0:164910:0:(namei.c:1202:ll_atomic_open()) VFS Op:name=f27M.sanity.5, dir=[0x2c0000404:0x312:0x0](00000000f3db4080), file 00000000c961ad14, open_flags 8441, mode 81b6 opened 0
      00000002:00010000:1.0:1662583867.631827:0:164910:0:(mdc_locks.c:1330:mdc_intent_lock()) (name: f27M.sanity.5,[0x2c0000404:0x316:0x0]) in obj [0x2c0000400:0x4d:0x0], intent: open|creat flags 0102102
      00010000:00010000:1.0:1662583867.631886:0:164910:0:(ldlm_request.c:1117:ldlm_cli_enqueue()) ### sending request ns: lustre-MDT0003-mdc-ffff9bc6d5d10000 lock: 00000000d0ba6210/0x7ffa82c0777bf3b lrc: 3/0,1 mode: --/CW res: [0x2c0000400:0x4d:0x0].0x0 bits 0x1/0x0 rrc: 2 type: IBT gid 0 flags: 0x0 nid: local remote: 0x0 expref: -99 pid: 164910 timeout: 0 lvb_type: 0
      00000100:00100000:1.0:1662583867.631905:0:164910:0:(client.c:1733:ptlrpc_send_new_req()) Sending RPC req@000000008539cc8e pname:cluuid:pid:xid:nid:opc:job bash:43186af5-3212-4914-bbc3-ccbe4f3cb72a:164910:1743343543387648:10.240.44.16@tcp:101:bash.0
      :
      00000002:00100000:1.0:1662583867.632559:0:164910:0:(mdc_locks.c:745:mdc_finish_enqueue()) @@@ op=3 disposition=17, status=-22  req@000000008539cc8e x1743343543387648/t0(0) o101->lustre-MDT0003-mdc-ffff9bc6d5d10000@10.240.44.16@tcp:12/10 lens 4624/608 e 0 to 0 dl 1662583874 ref 1 fl Complete:RQU/0/0 rc 301/301 job:'bash.0'
      00000002:00002000:1.0:1662583867.632567:0:164910:0:(mdc_locks.c:1212:mdc_finish_intent_lock()) D_IT dentry=f27M.sanity.5 intent=open|creat status=-22 disp=17: rc = 0
      

      but there isn't really any useful information in the MDS debug log (too low debug level, only dlmtrace enabled).

      VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
      sanity test_27M - (5) stripe count , should be 8 for append

      Attachments

        Issue Links

          Activity

            People

              wc-triage WC Triage
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: