From 3159a28f880bcbd7c2a45a843e72442578e5bd0f Mon Sep 17 00:00:00 2001 From: jgoerzen Date: Mon, 5 Sep 2022 00:59:39 +0000 Subject: [PATCH] --- doc/bugs/Files_recorded_with_other_file__39__s_checksums.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/bugs/Files_recorded_with_other_file__39__s_checksums.mdwn b/doc/bugs/Files_recorded_with_other_file__39__s_checksums.mdwn index 7dfaf33982..e74f155d8e 100644 --- a/doc/bugs/Files_recorded_with_other_file__39__s_checksums.mdwn +++ b/doc/bugs/Files_recorded_with_other_file__39__s_checksums.mdwn @@ -54,7 +54,7 @@ In a companion directory, .dtrash/files, 24 out of 719 files exhibited this issu I have not yet seen it outside .dtrash, but it will be many hours until this get process completes fully, as it needs to copy about 1TB of data. -In case you are wondering if there is a race condition with .dtrash: no. The only application that writes to it isn't running, and the last time a file was modified in there was over a year ago. +In case you are wondering if there is a race condition with .dtrash: no. The only application that writes to it isn't running, and the last time a file was modified in there was over a year ago. Also the content of the .info files is just JSON and a corresponding filename embedded in them, so it is very clear that the files on the filesystem are correct and the calculated checksums at issue here were never correct. ### What steps will reproduce the problem?