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

Improve error message handling when mirrored files are accessed by older clients

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Fix
    • Minor
    • None
    • Lustre 2.11.0
    • 9223372036854775807

    Description

      Issue extracted from the testing captured in LU-10286:

      I have a system configured as 2.11 servers, one 2.11 client and one 2.9.0 client
      1. on the 2.11 client, create 1 pfl file, 1 flr file with plain layout, and 1 flr file with composite layout
      2. on the 2.9 client, got these messages when try to access these files and when I do "ls -al" :

      [root@onyx-77 lustre]# ls
      foo-ext  foo-flr  foo-pfl  foo-plain-2.9
      [root@onyx-77 lustre]# ls -al
      [329391.090438] LustreError: 57728:0:(lov_internal.h:100:lsm_op_find()) unrecognized lsm_magic 0bd60bd0
      [329391.102999] LustreError: 57728:0:(lov_internal.h:100:lsm_op_find()) Skipped 3 previous similar messages
      [329391.115668] LustreError: 57728:0:(lov_pack.c:213:lov_verify_lmm()) bad disk LOV MAGIC: 0x0BD60BD0; dumping LMM (size=552):
      [329391.130044] LustreError: 57728:0:(lov_pack.c:213:lov_verify_lmm()) Skipped 3 previous similar messages
      [329391.142376] LustreError: 57728:0:(lov_pack.c:222:lov_verify_lmm()) FF0BFF0B2802000003000000010005000200000000000000000000000000000001000100100000000000000000000000FFFFFFFFFFFFFFFF10010000380000000000000000000000000000000000000001000200100000000000000000000000000010000000000048010000380000000000000000000000000000000000000002000200000000000000100000000000FFFFFFFFFFFFFFFFFF0100003800000000000000000000000000000000000000010003001000000000000000000000000000100000000000FF010000380000000000000000000000000000000000000002000300000000000000100000000000FFFFFFFFFFFFFFFFFF0100003800000000000000000000000000000000000000FF0BFF0B01000000030000000000000001040000020000000000100001000000040000000000000000000000000000000000000000000000FF0BFF0B01000000030000000000000001040000020000000000100001000000040000000000000000000000000000000000000001000000FF0BFF0B0100000003000000000000000104000002000000000010000200FFFF0000000000000000000000000000000000000000FFFFFFFFFF0BFF0B0100000003000000000000000104000002000000000010[329391.251564] LustreError: 57728:0:(lov_pack.c:222:lov_verify_lmm()) Skipped 3 previous similar messages
      [329391.266288] LustreError: 57728:0:(lcommon_cl.c:181:cl_file_inode_init()) Failure to initialize cl object [0x200000401:0x3:0x0]: -22
      [329391.283577] LustreError: 57728:0:(lcommon_cl.c:181:cl_file_inode_init()) Skipped 3 previous similar messages
      [329391.296622] LustreError: 57728:0:(llite_lib.c:2300:ll_prep_inode()) new_inode -fatal: rc -22
      [329391.307933] LustreError: 57728:0:(llite_lib.c:2300:ll_prep_inode()) Skipped 1 previous similar message
      ls: cannot access foo-ext: Invalid argument
      ls: cannot access foo-pfl: Invalid argument
      ls: cannot access foo-flr: Invalid argument
      total 8
      drwxr-xr-x  3 root root 4096 Dec 22 15:56 .
      drwxr-xr-x. 3 root root 4096 Dec 18 20:52 ..
      -?????????? ? ?    ?       ?            ? foo-ext
      -?????????? ? ?    ?       ?            ? foo-flr
      -?????????? ? ?    ?       ?            ? foo-pfl
      -rw-r--r--  1 root root    0 Dec 22 15:56 foo-plain-2.9
      [root@onyx-77 lustre]# 
      

      Andreas' thoughts: It probably makes sense to improve these error messages to consolidate them to at most one message per unknown magic, or similar. It probably isn't useful to dump the long hex string to the console.

      Attachments

        Issue Links

          Activity

            People

              yujian Jian Yu
              jgmitter Joseph Gmitter (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: