Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-51575

No space left on scratch PVC when importing fully allocated image

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • CNV v4.18.1
    • None
    • Storage Platform
    • None
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • ---
    • ---
    • Moderate
    • None

      Description of problem:

      When importing a fully expanded image into a PVC that matches its size, the process can fail due to insufficient usable space in the scratch PVC caused by the presence of the lost+found directory.

      Version-Release number of selected component (if applicable):

      4.18.0

      How reproducible:

      Always

      Steps to Reproduce:

      1.Create a PVC using rook-ceph (e.g., size = 512Mi).
      2.Import a fully expanded image that matches the PVC size (512Mi actual size).
      3.During the import process, the scratch PVC will fail due to insufficient usable space caused by lost+found. 

      Actual results:

      Import fails due to lack of space.

      Expected results:

      Import succeeds.

      Additional info:

      This issue is especially easy to replicate when using the VM manifest endpoint of the export API. When exporting a VM with block volumes, these are usually expanded to the capacity size by virt-launcher. Since the VM manifest endpoint recreates the original VM manifest (same size, e.g., 512Mi) but replaces the HTTP endpoints with the export server ones, these volumes will have an exact size of 512Mi, leading to a failed import due to the lost+found directory.

       

              rh-ee-alromero Alvaro Romero
              rh-ee-alromero Alvaro Romero
              Ahmad Hafi Ahmad Hafi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: