From owner-freebsd-fs Sat Jul 13 02:10:34 1996 Return-Path: owner-fs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA25278 for fs-outgoing; Sat, 13 Jul 1996 02:10:34 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA25259; Sat, 13 Jul 1996 02:10:27 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA26066; Sat, 13 Jul 1996 11:10:13 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA10257; Sat, 13 Jul 1996 11:10:13 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id KAA22966; Sat, 13 Jul 1996 10:21:11 +0200 (MET DST) From: J Wunsch Message-Id: <199607130821.KAA22966@uriah.heep.sax.de> Subject: Re: strangest weirdness To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Date: Sat, 13 Jul 1996 10:21:11 +0200 (MET DST) Cc: adam@veda.is (Adam David) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607130027.AAA07477@veda.is> from Adam David at "Jul 13, 96 00:27:54 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Adam David wrote: > I have also noticed that executables dump core often on client machines when > the files on the fileserver have been updated "under their feet". Okay I know > "if it hurts, don't do that", but why do these glitches occur? Terry will certainly jump in now and explain you that it would be better to move over the entire executable into local swap instead of relying on the ability to page it in from the NFS server. The latter is what we're doing right now -- so you are simply not expected to remove it on the server. The Unix semantics of ``a file will only be removed once the last reference to it disappeared'' don't work over NFS since the server simply doesn't know (and cannot know due to the statelessness of the protocol) which clients still hold references on some file. These semantics are being emulated in the case where you unlink a file on the client that has still other references, by renaming the file on the server first, and remove it later. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)