-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.13.z, 4.12.z, 4.11.z
-
None
This is a clone of issue OCPBUGS-22250. The following is the description of the original issue:
—
Description of problem:
- When using a large volume, it could not be cleaned to be reused.
Version-Release number of selected component (if applicable):
How reproducible:
- Create a new LocalVolume (20TB) - Attach the volume to a pod via PV--> PVC - Delete the pod - Delete de PVC - Review disk-manager logs
Steps to Reproduce:
- Create a new LocalVolume (20TB) - Attach the volume to a pod via PV--> PVC - Delete the pod - Delete de PVC -
Actual results:
I1020 09:30:11.473793 2419500 deleter.go:325] Cleanup pv "local-pv-591b00ae": StderrBuf - "mkfs.ext2: Size of device (0x1230c0000 blocks) /mnt/local-storage/minio-local-storage/scsi-35000c500d9e7604b too big to be expressed" I1020 09:30:11.473802 2419500 deleter.go:325] Cleanup pv "local-pv-591b00ae": StderrBuf - "\tin 32 bits using a blocksize of 4096." E1020 09:30:11.473820 2419500 deleter.go:286] exit status 1
Expected results:
- The volume should be wiped
Additional info:
Seems that this comes while calling mkfs before wiping the volume devices.
https://github.com/openshift/local-storage-operator/blob/910224d9f48be06b1f55890c93de472f7bd4bef0/hack/scripts/quick_reset.sh#L34C1-L38C42
Which by default is set to ext2 which might not work for large volumes:
### Manual mkfs:
-t, --type type
Specify the type of filesystem to be built. If not specified, the default filesystem type (currently ext2) is used
- Similar to https://access.redhat.com/solutions/66689
- blocks
-
-
- Closed
-
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
-
RHBA-2024:1045
OpenShift Container Platform 4.14.z extras update