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

Build: Debug symbols needed for the whole stack

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • Lustre 2.4.0
    • None
    • From the lbuild system as provided on the build server.
    • 3
    • 7562

    Description

      As seen from oprofile on Hyperion.

      PU: Intel Sandy Bridge microarchitecture, speed 1200 MHz (estimated)
      Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit mask of 0x00 (No unit mask) count 100000
      samples  %        app name                 symbol name
      20100    17.5058  zfs                      /zfs
      15546    13.5396  libcfs                   /libcfs
      9569      8.3340  zcommon                  /zcommon
      7959      6.9318  vmlinux-2.6.32-279.19.1.el6_lustre.x86_64 intel_idle
      5582      4.8616  spl                      /spl
      4149      3.6135  vmlinux-2.6.32-279.19.1.el6_lustre.x86_64 memmove
      3792      3.3026  vmlinux-2.6.32-279.19.1.el6_lustre.x86_64 mutex_lock
      2835      2.4691  vmlinux-2.6.32-279.19.1.el6_lustre.x86_64 mutex_unlock
      1954      1.7018  dm_mod                   /dm_mod
      

      There is a vmlinux (from the kernel-debuginfo package) but it is not clear where the rest of the symbols are.

      Everything we build should have debuginfo package that works with standard tools.

      In my local system I have pointed to source trees but on a far far away server this will be quite painful. It should be as simple as just installing the correct packages installed.

      The build that is currently deployed on Hyperion is, lustre-master-1340

      I didn't see any zfs related debug info packages.

      Attachments

        Activity

          People

            wc-triage WC Triage
            keith Keith Mannthey (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: