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 ZFS counts a new file's blocks only seconds after the write. The count can land in under a second, so both now say up to seconds after the write, as the comment on `diskSizeOf` already does. Model: opus-5-5
2026-11-03 05:00:51 +01:00
parent 30dae35c51
commit f52bbe5d95
3 changed files with 9 additions and 4 deletions
@@ -407,9 +407,9 @@ operands:
  is what makes a daily rescan cheap.
 - When such a file's size on disk differs from its recorded `disk_size`, `scan`
  updates `disk_size` alone. It still does not read the file, and counts it as
-  unchanged. ZFS, for example, counts a new file's blocks only seconds after the
-  write. A block is the unit in which a filesystem allocates disk space. A file
-  scanned within those seconds gets its real `disk_size` at the next scan.
+  unchanged. ZFS, for example, counts a new file's blocks up to seconds after
+  the write. A block is the unit in which a filesystem allocates disk space. A
+  file scanned within those seconds gets its real `disk_size` at the next scan.
 - `scan` hashes a file again when its size differs or its mtime is newer. The
  mtime is compared to the nanosecond, as finely as the filesystem records it. A
  same-size rewrite counts as a change whenever the filesystem gives it a later