Expected behavior
When creating a Quick Format file container with --no-size-check, VeraCrypt should allow the logical container size to exceed the currently available free space on the host filesystem.
Observed behavior
VeraCrypt 1.26.29 rejects the requested container size when it exceeds the currently available host filesystem space, even when --no-size-check is specified.
The host filesystem has approximately 53 GiB available:
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 143G 83G 53G 61% /
A 52 GiB Quick Format container is accepted, while a 75 GiB container is rejected with:
Error: Incorrect volume size
The behavior appears to track the amount of available disk space despite --no-size-check.
Steps to reproduce
- Use a filesystem with less free space than the desired logical VeraCrypt container size. In my case, / has approximately 53 GiB available:
df -h
/dev/sda1 143G 83G 53G 61% /
- Create a Quick Format container smaller than the available space:
veracrypt --text --create vault.hc
--size=52G
--volume-type=normal
--encryption=AES
--hash=SHA-512
--filesystem=ext4
--quick
--no-size-check
--random-source=/dev/urandom
The 52 GiB size is accepted.
-
Remove the test container if necessary and attempt to create a 75 GiB Quick Format container:
veracrypt --text --create vault.hc
--size=75G
--volume-type=normal
--encryption=AES
--hash=SHA-512
--filesystem=ext4
--quick
--no-size-check
--random-source=/dev/urandom
-
VeraCrypt immediately returns:
Error: Incorrect volume size
Removing --filesystem=ext4 does not appear necessary to trigger the issue; the rejection occurs while validating the requested volume size.
The documented purpose of --no-size-check is to disable the check of container size against available disk free space, so I would expect the 75 GiB sparse/Quick Format container to be permitted.
Screenshots
Your Environment
Please tell us more about your environment
VeraCrypt version: 1.26.29
Operating system and version: Debian Linux 13
System type: 64-Bit
Expected behavior
When creating a Quick Format file container with --no-size-check, VeraCrypt should allow the logical container size to exceed the currently available free space on the host filesystem.
Observed behavior
VeraCrypt 1.26.29 rejects the requested container size when it exceeds the currently available host filesystem space, even when --no-size-check is specified.
The host filesystem has approximately 53 GiB available:
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 143G 83G 53G 61% /
A 52 GiB Quick Format container is accepted, while a 75 GiB container is rejected with:
Error: Incorrect volume size
The behavior appears to track the amount of available disk space despite --no-size-check.
Steps to reproduce
df -h
/dev/sda1 143G 83G 53G 61% /
veracrypt --text --create vault.hc
--size=52G
--volume-type=normal
--encryption=AES
--hash=SHA-512
--filesystem=ext4
--quick
--no-size-check
--random-source=/dev/urandom
The 52 GiB size is accepted.
Remove the test container if necessary and attempt to create a 75 GiB Quick Format container:
veracrypt --text --create vault.hc
--size=75G
--volume-type=normal
--encryption=AES
--hash=SHA-512
--filesystem=ext4
--quick
--no-size-check
--random-source=/dev/urandom
VeraCrypt immediately returns:
Error: Incorrect volume size
Removing --filesystem=ext4 does not appear necessary to trigger the issue; the rejection occurs while validating the requested volume size.
The documented purpose of --no-size-check is to disable the check of container size against available disk free space, so I would expect the 75 GiB sparse/Quick Format container to be permitted.
Screenshots
Your Environment
Please tell us more about your environment
VeraCrypt version: 1.26.29
Operating system and version: Debian Linux 13
System type: 64-Bit