Jump to content
  • [6.9.2] Invalid Access Timestamp on File


    TimTheSettler
    • Annoyance

    I'm not entirely sure where this problem is coming from.

     

    I have a few Windows 10 desktop machines.  All connect to an unRAID server where I save all my files.  I also have an older Windows machine where I back up all of the data from the unRAID server to that older Windows machine.

     

    On one of the Windows 10 machines I can open various files from the unRAID server but when I save those files the "last access timestamp" is set to the "max date" (https://en.wikipedia.org/wiki/Year_2038_problem).  See the attached file.  This causes problems with the synchronization program that I use.  If I copy the file from unRAID to this Windows 10 machine and edit it there then the "last access timestamp" is set correctly.  I can copy the file back to unRAID where my synchronization program will pick it up.

     

    On my other two Windows 10 machines if I open the same files and save them the "last access timestamp" is set correctly.  So for some reason one of the Windows 10 machines is "weird".

     

    All three Windows 10 machines have the exact same version of Windows (19042.1288) and all three Windows 10 machines have the "last access" turned on (system managed).

     

    C:\Users\Tim>fsutil behavior query disablelastaccess
    DisableLastAccess = 2  (System Managed, Disabled)

     

    Is it possible that this is some lingering problem from the Linux 2038 fix in version 5.10 (https://linux.slashdot.org/story/20/10/17/2237236/linux-510-solves-the-year-2038-problem-until-2486) or is there something wrong with this one "weird" Windows machine?  There's even a program out there to manually fix this timestamp problem (https://backupchain.com/i/file-date-repair-tool-v1-0-fixes-broken-invalid-time-stamps).  The fact that this program exists proves that I'm not the only person to have this problem and yet if you search Google you don't find very much info about it.  I'm stumped.

     

    Thanks,

    Tim.

     

     

    File Accessed 2038 (Modified).png




    User Feedback

    Recommended Comments

    There are no comments to display.



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...