Say ZFS counts a new file's blocks up to seconds after the write (closes #152)

`README.md` and a comment in `scan.go` said "only seconds after the write". That is false, because the count can land in under a second. Both now agree with the comment on `diskSizeOf` in `scan_test.go`. Model: opus-5-5
2026-11-03 03:30:33 +00:00
parent 30dae35c51
commit a00b97e299
3 changed files with 9 additions and 4 deletions
@@ -29,6 +29,11 @@
 Newest first. An entry ends with its date and its issue or branch, where those
 are known.

+- `README.md` and a comment in `scan.go` no longer say ZFS counts a new file's
+  blocks only seconds after the write. The count can land in under a second.
+  Both now say up to seconds after the write, as the comment on `diskSizeOf` in
+  `scan_test.go` does (2026-11-03, https://git.eeqj.de/sneak/sfdupes/issues/152)
+
 - The three disk size tests in `scan_test.go` no longer fail at random on ZFS.
  `unix.Sync` can return before ZFS has counted a file's blocks, and one ZFS
  commit can take a file through several sizes. The test that needs the size to