From: usenet.16@scottsonline.org.uk.invalid   
      
   Hmmm.   
      
   Checking over things, I found some old files with dates in the future.   
   One directory lists as:   
      
   CD> ls -li   
   total 36   
   3671727 -rw-rw-r-- 1 mike mike  1230 Oct 16  2018 cd1.k3b   
   3671728 -rw-rw-r-- 1 mike mike  1160 Oct 16  2018 cd1.k3b.files   
   3671729 -rw-r--r-- 1 mike mike   137 Oct 16  2018 k3b2list.sh   
   3671730 -rw-r--r-- 1 mike mike 17873 Feb  7  2106 maindata.xml   
   3671731 -rw-r--r-- 1 mike mike    17 Feb  7  2106 mimetype   
      
      
   Note the future dates for the last two. This stuff has been left around   
   since 2018, unmodified (by me, at least). The contents look reasonable,   
   so it's just the metadata messed up - they seem to be the only two files   
   affected.   
      
   The data was on a freebsd machine until a few weeks ago, when the whole   
   lot was rsync'd from spinning rust to the present SSD on a mint server.   
      
   A bit worrying: freebsd failure? rsync failure? SSD failure? linux   
   failure? Gremlins?   
      
   But how can anyone possibly realistically detect this sort of thing?   
   With an unknown cause?   
      
      
   --   
   Mike Scott   
   Harlow, England   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)