c/mirror_zfs
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_zfs.git synced 2026-05-22 18:40:43 +03:00
Code Issues Packages Projects Releases Wiki Activity

Corrected oversight in ZERO_RANGE behavior

Browse Source 
It turns out, no, in fact, ZERO_RANGE and PUNCH_HOLE do
have differing semantics in some ways - in particular,
one requires KEEP_SIZE, and the other does not.

Also added a zero-range test to catch this, corrected a flaw
that made the punch-hole test succeed vacuously, and a typo
in file_write.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Closes #13329 
Closes #13338
This commit is contained in:
Rich Ercolani
2022-04-20 19:07:03 -04:00
committed by Brian Behlendorf
parent 361dc138b1
commit c220771a47
8 changed files with 171 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/zfs-tests/cmd/file_write/file_write.c
+1 -1
View File
@@ -251,7 +251,7 @@ usage(char *prog)
"\t[-s offset] [-c write_count] [-d data]\n\n"
"Where [data] equal to zero causes chars "
"0->%d to be repeated throughout, or [data]\n"
"equal to 'R' for psudorandom data.\n",
"equal to 'R' for pseudorandom data.\n",
prog, DATA_RANGE);
exit(1);