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

Interop testing results for 1.8.5.54 clients with Lustre 2.0.59 servers

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • Lustre 2.1.0
    • Lustre 1.8.6
    • None
    • 4 OSS, each with 7 OSTS with one MDS with a disk devoted to a MDT and another disk devoted to the MGS; all running lustre 2.0.59. I have 4 clients running lustre 1.8.5.54

    Description

      These are the results of running the b1_8 acc_sm test. I also listed the results at https://bugzilla.lustre.org/show_bug.cgi?id=21367.

      sanity 64b - bug 22703
      sanity 72b - bug 24226
      replay-single 65a - bug 19960
      sanity-quota - totally broken. Does not work at all. Locks up clients

      obdfilter-survey - locks the client up. No debug output
      config-sanity 55,56,57 - no bug report yet. Seeing the following error

      LustreError: 13996:0:(mdt_handler.c:4521:mdt_init0()) CMD Operation not allowed in IOP mode
      LustreError: 13996:0:(obd_config.c:495:class_setup()) setup lustre-MDT0001 failed (-22)
      LustreError: 13996:0:(obd_config.c:1338:class_config_llog_handler()) Err -22 on cfg command:
      Lustre: cmd=cf003 0:lustre-MDT0001 1:lustre-MDT0001_UUID 2:1 3:lustre-MDT0001-mdtlov 4:f
      LustreError: 15b-f: MGC10.36.230.2@o2ib: The configuration from log 'lustre-MDT0001'failed from the
      MGS (-22). Make sure this client and the MGS are running compatible versions of Lustre.
      LustreError: 15c-8: MGC10.36.230.2@o2ib: The configuration from log 'lustre-MDT0001' failed (-22).
      This may be the result of communication errors between this node and the MGS, a bad configuration,
      or other errors. See the syslog for more information.

      I will provide more info and logs as very soon.

      Attachments

        Activity

          People

            yong.fan nasf (Inactive)
            simmonsja James A Simmons
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: