Subject: Re: [BUG] NFS no longer updates file modification times  
	appropriately
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20040604162410.569c7ecc@dell_ss3.pdx.osdl.net>
References: <1086297112.3659.3.camel@lade.trondhjem.org>
	 <20040604132355.GA31710@tsunami.ccur.com>
	 <1086390495.4161.43.camel@lade.trondhjem.org>
	 <20040604162410.569c7ecc@dell_ss3.pdx.osdl.net>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Message-Id: <1086392275.4161.52.camel@lade.trondhjem.org>
Mime-Version: 1.0
Date: Fri, 04 Jun 2004 19:37:55 -0400
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 660
Lines: 17

P? fr , 04/06/2004 klokka 19:24, skreiv Stephen Hemminger:

> What about fsync()?

There were no changes to fsync() between 2.6.5 and 2.6.6. In any case,
Joe's test program did not use fsync() (that was very much the problem).
Any use of either close() or fsync() on the client will cause the
mtime/ctime to be updated on the server, and that change should
immediately propagate back to the client.

Cheers,
  Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/