-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
None
-
5
-
False
-
-
False
-
---
-
---
-
-
Storage Core Sprint 248, Storage Core Sprint 249, Storage Core Sprint 250, Storage Core Sprint 252, Storage Core Sprint 253, Storage Core Sprint 254
-
No
Description of problem:
When cloning a DV with a large image on ocs block the clone fail with an error in the logs:
/usr/bin/tar: disk.img: Cannot write: No space left on device
/usr/bin/tar: Exiting with failure status due to previous errors
When use a larger pool, the clone do succeeded but in previous versions it works with the same size (an same image).
Version-Release number of selected component (if applicable):
4.14
How reproducible:
100%
Steps to Reproduce:
1. Create a DV with large image (used size 70Gi) 2. Clone the DV 3.
Actual results:
clone get stuck in the middle
Expected results:
DV cloned successfully
Additional info:
oc logs cdi-upload-tmp-pvc-* I1129 18:00:14.598514 1 uploadserver.go:74] Running server on 0.0.0.0:8443 I1129 18:00:19.420309 1 uploadserver.go:389] Content type header is "filesystem-clone" I1129 18:00:19.420454 1 util.go:207] begin untar to /data... I1129 18:00:19.420468 1 util.go:213] running untar cmd: [/usr/bin/tar --preserve-permissions --no-same-owner -xvC /data] I1129 18:08:02.239801 1 util.go:220] STDOUT disk.img I1129 18:08:02.239878 1 util.go:221] STDERR /usr/bin/tar: disk.img: Cannot write: No space left on device /usr/bin/tar: Exiting with failure status due to previous errors E1129 18:08:02.239927 1 util.go:222] exit status 2 E1129 18:08:02.239977 1 uploadserver.go:402] Saving stream failed: error unarchiving to /data: exit status 2
- is cloned by
-
CNV-46594 [4.12] Clone takes more space in 4.12 - on hostpath-csi-pvc-block storage
- ASSIGNED
-
CNV-41473 [4.15] Clone takes more space in 4.14 - on hostpath-csi-pvc-block storage
- Closed
-
CNV-41474 [4.16] Clone takes more space in 4.14 - on hostpath-csi-pvc-block storage
- Closed
- links to
-
RHEA-2024:130908 OpenShift Virtualization 4.14.6 Images
- mentioned on