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

Move hole punch test from FS creation to opening

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.8.0
    • None
    • fs, supportability
    • None

    Description

      Currently the hole punch test happens when the Kudu filesystem is created. However, we've seen some cases where users have copied existing LBM instances to new filesystems that didn't support hole punching. Doing the test at open time (or maybe at create and open time) would help detect such cases.

      We probably want to add some conditions on this though:

      1. Skip in on read-only filesystems.
      2. Skip it in unit tests (unnecessary slowdown?).

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. KUDU-2536 Make log_block_manager_test_hole_punching work again

          • Major - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              adar Adar Dembo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: