diff options
| author | Rich Ercolani <[email protected]> | 2022-04-20 19:07:03 -0400 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2022-04-21 16:58:07 -0700 |
| commit | c220771a47e4206fb43e6849957657c9504b1b14 (patch) | |
| tree | 54b352c60e701179759af2e70ac704c4fda384d2 /tests/zfs-tests/cmd/file_write | |
| parent | 361dc138b1bdd6b7ec32fbd74b775c55c595f45f (diff) | |
Corrected oversight in ZERO_RANGE behavior
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 <[email protected]>
Signed-off-by: Rich Ercolani <[email protected]>
Closes #13329
Closes #13338
Diffstat (limited to 'tests/zfs-tests/cmd/file_write')
| -rw-r--r-- | tests/zfs-tests/cmd/file_write/file_write.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/zfs-tests/cmd/file_write/file_write.c b/tests/zfs-tests/cmd/file_write/file_write.c index 60893c34f..9d2e71b67 100644 --- a/tests/zfs-tests/cmd/file_write/file_write.c +++ b/tests/zfs-tests/cmd/file_write/file_write.c @@ -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); |