[SSI-devel] [ ssic-linux-Bugs-2010447 ] OpenSSI fails the glibc tst-atime test
Brought to you by:
brucewalker,
rogertsang
From: SourceForge.net <no...@so...> - 2008-10-19 15:33:06
|
Bugs item #2010447, was opened at 2008-07-04 11:19 Message generated for change (Comment added) made by hughesj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=2010447&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Filesystem Group: default Status: Open Resolution: None Priority: 1 Private: No Submitted By: John Hughes (hughesj) Assigned to: Nobody/Anonymous (nobody) Summary: OpenSSI fails the glibc tst-atime test Initial Comment: CFS doesn't keep the atime (last accessed time) field up to date. This is a known limitation, I'm just reporting it here so it doesn't get forgotten about. Maybe as a workaround we could pretend that cfs filesystems were mounted with the noatime option? To reproduce: $ cc tst-atime.c $ ./a.out atime has not changed ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2008-10-19 17:32 Message: Simple idea, just do this at user level by remounting the fs with an explicit noatime option: mount -o remount,noatime / doesn't work because statvfs reads /proc/mounts to find the mount options and some of the weird crud we have hanging around confuses it: # cat /proc/mounts rootfs / rootfs rw 0 0 /dev2/root2 / cfs rw,noatime,chard,node=1 0 0 ... Which is the real root? Apparently statvfs thinks it's the first one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=2010447&group_id=32541 |