--no-size-check ignored when creating sparse/Quick Format container larger than available disk space
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by tracing the CLI volume-creation validation for --size and --no-size-check, then follow where available filesystem space is checked during Quick Format creation. Reproduce on Debian Linux with a filesystem whose free space is below the requested size, using the provided 52 GiB and 75 GiB commands. Done when the larger sparse container is accepted with --no-size-check while ordinary size validation still behaves as intended.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- C
- 星标
- 11.7k
- 派生
- 1.4k
- 平均合并
- 1 天 1 小时
- 30 天内合并 PR
- 28
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
veracrypt/VeraCrypt 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
bug
难度 5/5 一周以上 新手友好度 32/100
veracrypt/VeraCrypt#1995 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 42/100
veracrypt/VeraCrypt#1993 · 2 条评论 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 55/100
veracrypt/VeraCrypt#1991 · 1 条评论 ·
维护者通常 1 天内回复
查看 veracrypt/VeraCrypt 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
bug game: 01008BA02525A000 ios
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
area/ysql kind/bug priority/medium status/awaiting-triage
难度 2/5 1-3 小时 新手友好度 78/100
yugabyte/yugabyte-db#37523 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 3 天内回复
-
难度 1/5 1 小时以内 新手友好度 65/100
ly05010419/MacNativeGames#2079 ·
维护者通常 1 天内回复