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

changelog catalog corruption if all possible records is define

Details

    • 3
    • 9223372036854775807

    Description

      After our last lustre upgrade, On tera100 and tgcc site, some
      lustre fs have meet the same corruption on the changelog_catalog
      The robinhood node panic like in the LU-6471 and the crash analyze
      show that is the changelog-catalog file that have a corruption.
      The file is too big than the maximum size of this type of file and
      the record who produces the panic is not in the right place.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-7138 LBUG: (osd_handler.c:1017:osd_trans_start()) ASSERTION( get_current()->journal_info == ((void *)0) ) failed:

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. LU-6634 (osd_handler.c:901:osd_trans_start()) ASSERTION( get_current()->journal_info == ((void *)0) ) failed: when reaching Catalog full condition

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. LU-7241 sanity test_60a: there are no more free slots in catalog

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. LU-6954 LustreError: 12934:0:(mdd_device.c:305:mdd_changelog_llog_init()) fsrzb-MDD0000: changelog init failed: rc = -5

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-4528 osd_trans_exec_op()) ASSERTION( oti->oti_declare_ops_rb[rb] > 0 ) failed: rb = 0

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. LU-7329 sanity test_60a timeouts with “* invoking oom-killer”

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            [LU-6556] changelog catalog corruption if all possible records is define
            pjones Peter Jones made changes -
            Link New: This issue is related to LDEV-37 [ LDEV-37 ]
            pjones Peter Jones made changes -
            Link Original: This issue is related to LDEV-142 [ LDEV-142 ]
            pjones Peter Jones made changes -
            Link New: This issue is related to LDEV-143 [ LDEV-143 ]
            pjones Peter Jones made changes -
            Link Original: This issue is related to LDEV-18 [ LDEV-18 ]
            adilger Andreas Dilger added a comment -

            Backported of the http://review.whamcloud.com/14912 patch also need the patch http://review.whamcloud.com/17052 "LU-7329 obdclass: sync device to flush journal callbacks" patch to avoid introducing test failures in sanity test_60a.

            adilger Andreas Dilger added a comment - Backported of the http://review.whamcloud.com/14912 patch also need the patch http://review.whamcloud.com/17052 " LU-7329 obdclass: sync device to flush journal callbacks" patch to avoid introducing test failures in sanity test_60a.
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-7329 [ LU-7329 ]
            pjones Peter Jones made changes -
            Link Original: This issue is related to JFC-10 [ JFC-10 ]
            pjones Peter Jones made changes -
            Link New: This issue is related to JFC-14 [ JFC-14 ]
            pjones Peter Jones made changes -
            Link New: This issue is related to LDEV-142 [ LDEV-142 ]
            jfc John Fuchs-Chesney (Inactive) made changes -
            Link New: This issue is related to JFC-10 [ JFC-10 ]

            People

              bfaccini Bruno Faccini (Inactive)
              apercher Antoine Percher
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: