FAT isn't meant to record file access time, but the FAT filesystem I have in a VeraCrypt container file does. Why is this?
This was before I opened the file /run/media/veracrypt1/test:
~ $ stat /run/media/veracrypt1/test File: /run/media/veracrypt1/test Size: 351 Blocks: 2 IO Block: 1024 regular file Device: 7,1 Inode: 42223 Links: 1 Access: (0700/-rwx------) Uid: ( 1000/ emma) Gid: ( 1000/ emma) Access: 2025-10-26 01:00:00.000000000 +0100 Modify: 2025-10-26 13:34:36.000000000 +0000 Change: 2025-10-26 13:34:36.000000000 +0000 Birth: 2025-10-26 13:57:51.270000000 +0000 This was after I opened the file /run/media/veracrypt1/test:
~ $ stat /run/media/veracrypt1/test File: /run/media/veracrypt1/test Size: 351 Blocks: 2 IO Block: 1024 regular file Device: 7,1 Inode: 42223 Links: 1 Access: (0700/-rwx------) Uid: ( 1000/ emma) Gid: ( 1000/ emma) Access: 2025-11-19 00:00:00.000000000 +0000 Modify: 2025-10-26 13:34:36.000000000 +0000 Change: 2025-10-26 13:34:36.000000000 +0000 Birth: 2025-10-26 13:57:51.270000000 +0000
,noatimeto the mount options, if it is on Linux and if FAT supports that option) in case you don't need the access date. This will diminish the amount of disk writes (which is important for those on usb keys or ssd medias, for exemple, as the number of overall possible writes on some section of the media could be limited) and could also save quite a lot of time spent writing those dates (especially on slow medias such as usb keys)