[DragonFlyBSD - Bug #2056] (Closed) HAMMER does not update file access time after read

[John Marino via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2056 has been updated by John Marino.

Status changed from New to Closed

Both hammer and UFS give the same result given the provided test (as would be expected).

----------------------------------------
Bug #2056: HAMMER does not update file access time after read
http://bugs.dragonflybsd.org/issues/2056

Author: John Marino
Status: Closed
Priority: Normal
Assignee: Matthew Dillon
Category: 
Target version: 


During the development of the upgrade of grep to version 2.7, it was observed 
that the HAVE_WORKING_O_NOATIME value was defined as 0 for the i386 platform and 
1 for the x86_64 platform.  The i386 platform filesystem was UFS and the other 
was configured with Hammer.

The grep configuration script uses standard gnu tests.  The one used to derive 
the O_NOATIME value is located at 
http://leaf.dragonflybsd.org/~marino/fctnl_check.c

After some testing, swildner confirmed that Hammer doesn't update the file 
access time after data (more than 0 bytes) is read from a file.  He believes 
that this behavior is not simply a convention, but covered by a standard.  Since 
Hammer isn't exhibiting the expected behavior, it should be considered a bug.

Moreover, every gnu configure script that is run on a system with Hammer will 
produce the wrong value for O_NOATIME support, and thus may cause unexpected 
behavior when the software compiles.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account