Re: File cache effecting access time...

Hi,

> The reason I ask is I want to test my hypothesis that
> the 'last accessed' timestamp is not refreshed when a file is cached...

Note that on NTFS, the last accessed time resolution is 1 hour. Maybe this
is why you think it hasn't been refreshed?

Complete quote from MSDN:

"Note Not all file systems can record creation and last access time and not
all file systems record them in the same manner. For example, on Windows NT
FAT, create time has a resolution of 10 milliseconds, write time has a
resolution of 2 seconds, and access time has a resolution of 1 day (really,
the access date). On NTFS, access time has a resolution of 1 hour.
Therefore, the GetFileTime function may not return the same file time
information set using the SetFileTime function. Furthermore, FAT records
times on disk in local time. However, NTFS records times on disk in UTC, so
it is not affected by changes in time zone or daylight saving time."

--

Mikko Noromaa (mikkon@xxxxxxxxxxxx)
- SQL in Excel, check out ExcelSQL! - see http://www.excelsql.com -




"djohnson" <programmer123@xxxxxxx> wrote in message
news:1136907802.377427.186310@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi, I doubt anyone can help me, but I understand Windows uses System
> RAM to cache commonly used files, and was wondering how to remove a
> specific file. The reason I ask is I want to test my hypothesis that
> the 'last accessed' timestamp is not refreshed when a file is cached...
> I'd really like the 'last accessed' time to be accurate, accuracy is
> good right especially in the computer world.
>
> On a related note I also wonder if anyone thinks if a lot of caching
> will become obsolete when RAM drives begin replacing HDs.
>
> Dave
>


.

Relevant Pages

  • RE: System Failure Stop Error
    ... unexpected shutdown of this computer is: System Failure: Stop error ... Reason Code: 0x805000f ... | Timestamp: unavailable ...
    (microsoft.public.windows.server.sbs)
  • Re: system crash during file copy to a floppy with bad sectors
    ... this is generally a question of resilience of individual file systems to on-disk corruption and failures. ... UFS is quite tricky to make robust against disk destruction, since it relies on strong consistenty guarantees for performance reasons. ... FAT, on the other hand, is a file system we should be able to make more robust quite a bit more easily. ... The reason FAT is particularly interesting, of course, is its widespread use on removable media such as USB sticks. ...
    (freebsd-stable)
  • System Failure Stop Error
    ... The reason supplied by user EVENTS\Administrator for the last ... Frame IP not in any known module. ... Timestamp: unavailable ... Checksum: 00000000 ...
    (microsoft.public.windows.server.sbs)
  • Re: isofs/cd9660 -> relocate to fs/isofs/cd9660?
    ... file systems to the fs tree. ... One good reason not to move things around in the kernel tree is that it's not just kernel code that is affected -- userland code is also affected, and if there are third party apps that use kernel include files, they need to be updated. ...
    (freebsd-current)
  • RE: memory mapped packet capturing - bpf replacement ?
    ... > There's no reason why the time has to be in microseconds or ... > even that it must be adjusted to realtime. ... I pointed out the timestamp issue only because it will penalize ...
    (freebsd-hackers)