From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trond Myklebust Subject: Re: IS_NOCMTIME and setting of ctime and mtime on remote servers Date: Mon, 29 Aug 2005 11:41:52 -0700 Message-ID: <1125340912.8105.10.camel@lade.trondhjem.org> References: <431342FC.20708@austin.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from pat.uio.no ([129.240.130.16]:42458 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S1751279AbVH2SmC convert rfc822-to-8bit (ORCPT ); Mon, 29 Aug 2005 14:42:02 -0400 To: Steve French In-Reply-To: <431342FC.20708@austin.rr.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org m=C3=A5 den 29.08.2005 Klokka 12:16 (-0500) skreiv Steve French: > NFS is the only place that sets NOCMTIME on inodes in its fhget routi= ne=20 > IIRC. >=20 > What is the exact intent of this? Does it stay set (so mtime and cti= me=20 > updates are never sent to the server) or does it get reset somewhere = (I=20 > did not see where nfs turned it off so presumably even explicit sets = of=20 > the time are ignored by default?)? NOCMTIME just turns off the inode_update_time() crapola. It has nothing to do with explicit sets of the time which are done through the utimes(= ) syscall. IOW: it turns off all those unwanted VFS updates of mtime/ctime which would otherwise screw up data and metadata cache revalidation. Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html