From owner-freebsd-hackers Wed Jan 2 17:47: 7 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (pop-mu-2-2-dialup-129.freesurf.ch [194.230.131.129]) by hub.freebsd.org (Postfix) with ESMTP id B565F37B421 for ; Wed, 2 Jan 2002 17:46:47 -0800 (PST) Received: from beerswilling.netscum.dyndns.dk (dcf77-zeit.netscum.dyndns.dk [172.27.72.27] (may be forged)) by dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (8.11.6/8.11.6) with ESMTP id g031cAc00218 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified FAIL) for ; Thu, 3 Jan 2002 02:38:12 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Received: (from root@localhost) by beerswilling.netscum.dyndns.dk (8.11.6/8.11.6) id g031c9Q00217; Thu, 3 Jan 2002 02:38:09 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Date: Thu, 3 Jan 2002 02:38:09 +0100 (CET) Message-Id: <200201030138.g031c9Q00217@beerswilling.netscum.dyndns.dk> From: BOUWSMA Beery To: freebsd-hackers@freebsd.org Subject: more observations on nullfs filesystem Organization: Men not wearing any pants that dont shave X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: TDC Suisse AG, Rumlang X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [replies sent directly to me may timeout and bounce, since I'm not online as often as I should be, but I'll check the list archives] Guten Morgen This was tried under -current (and probably -stable too) Should a nullfs mount handle options the way that one would expect from a normal filesystem mount? In particular, I have a read-only nullfs mount, but accesses to that read-only filesystem result in the atime being updated on the True Filesystem. Remounting the nullfs with `noatime' makes no difference -- again accessing files in the read-only directories result in updates of the Real Filesystem. Only by remounting the original fs with `noatime' do I get the wanted result, with the drawback that not only are accesses via the nullfs path, as desired, but all other accesses to the original filesystem get ignored. Specifically, I have system source in a /usr/local/system/source directory, but I've nullfs mounted that read-only on /usr/src and want to eliminate pretty much all updates to the /usr/local/... filesystem when building the world. Or is this something that the nullfs mount will not do, keeping atime updates from reaching the layer below, no matter whether read-only or noatime or anything similar is specified? thanks barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message