From owner-freebsd-fs@FreeBSD.ORG Mon Jul 4 00:21:27 2005 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC11016A41C for ; Mon, 4 Jul 2005 00:21:27 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 976F343D46 for ; Mon, 4 Jul 2005 00:21:25 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j640SNlx003770; Sun, 3 Jul 2005 18:28:23 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42C88121.8010602@samsco.org> Date: Sun, 03 Jul 2005 18:21:53 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephan Uphoff References: <20050703181616.GC89744@cvs.freesbie.org> <42C83643.4010506@samsco.org> <20050703201621.GD89744@cvs.freesbie.org> <1120425831.77984.37993.camel@palm> <42C87CAE.7080802@samsco.org> <1120436351.77984.38195.camel@palm> In-Reply-To: <1120436351.77984.38195.camel@palm> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-fs@freebsd.org Subject: Re: [saturnero@freesbie.org: Weird behaviour of mount_unionfs with executables] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jul 2005 00:21:27 -0000 Stephan Uphoff wrote: > On Sun, 2005-07-03 at 20:02, Scott Long wrote: > >>Stephan Uphoff wrote: >> >>>I suspect the changes in revision 1.272 of kern_exec.c trigger the >>>copy operation. >>> >>>Looks like you need a noatime option for union_fs. >>> >>>Stephan >> >>Does this mean that every vnode that gets executed gets dirtied and all >>its pages resynced to the backing store, or just the inode block? > > > The kernel calls VOP_SETATTR to set the access time of the file. > union_fs detects that it does not have an upper layer copy of the file > to modify the attributes on and decides to copy it. > The vm layer does not (directly) come into play on this. > > Stephan > Ok, so this is just a limitation of unionfs, not the vnode pager. You had me scared that we'd be doing a whole lot of needless disk i/o. Scott