Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-1508

Log block manager triggers ext4 hole punching bug in el6

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.9.0
    • Fix Version/s: 1.2.0
    • Component/s: fs
    • Labels:
      None
    • Target Version/s:

      Description

      I've experienced many times that when I reboot an el6 node that was running Kudu tservers, fsck reports issues like:

      data6 contains a file system with errors, check forced.
      data6: Interior extent node level 0 of inode 5259348:
      Logical start 154699 does not match logical start 2623046 at next level.

      After some investigation, I've determined that this is due to an ext4 kernel bug: https://patchwork.ozlabs.org/patch/206123/

      Details in a comment to follow.

        Attachments

        1. replay_container.py
          3 kB
          Adar Dembo
        2. pbc_dump.txt
          229 kB
          Adar Dembo
        3. filefrag.txt
          9 kB
          Adar Dembo
        4. e9f83e4acef3405f99d01914317351ce.metadata
          535 kB
          Todd Lipcon
        5. debugfs.txt
          0.4 kB
          Adar Dembo

          Activity

            People

            • Assignee:
              adar Adar Dembo
              Reporter:
              tlipcon Todd Lipcon
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: