Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: David Lang <david <at> lang.hm>
Subject: Re: page fault scalability (ext3, ext4, xfs)
Newsgroups: gmane.comp.file-systems.xfs.general
Date: Monday 19th August 2013 23:23:23 UTC (over 4 years ago)
On Fri, 16 Aug 2013, Dave Chinner wrote:

> The problem with "not exported, don't update" is that files can be
> modified on server startup (e.g. after a crash) or in short
> maintenance periods when the NFS service is down. When the server is
> started back up, the change number needs to indicate the file has
> been modified so that clients reconnecting to the server see the
> change.
>
> IOWs, even if the NFS server is not up or the filesystem not
> exported we still need to update change counts whenever a file
> changes if we are going to tell the NFS server that we keep them...

This sounds like you need something more like relctime rather than noctime,

something that updates the time in ram, but doesn't insist on flushing it
to 
disk immediatly, updating when convienient or when the file is closed.

David Lang

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
 
CD: 15ms