From owner-freebsd-current Wed Dec 15 23:51: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 834FA1557D for ; Wed, 15 Dec 1999 23:51:06 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA14569; Thu, 16 Dec 1999 08:50:59 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Andrew Gallatin , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-reply-to: Your message of "Wed, 15 Dec 1999 23:43:06 PST." <199912160743.XAA49890@apollo.backplane.com> Date: Thu, 16 Dec 1999 08:50:59 +0100 Message-ID: <14567.945330659@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912160743.XAA49890@apollo.backplane.com>, Matthew Dillon writes: > >:> NFS uses the kernel 'boottime' structure to generate its version id. >:> Now normally you might believe that this structure, once set, will >:> never change. The authors of NFS certainly make that assumption! >: >:Is this another case of "lets assume the time of day is a random number" or >:is there any underlying assumption about time in this ? >: >:-- >:Poul-Henning Kamp FreeBSD coreteam member >:phk@FreeBSD.ORG "Real hackers run -current on their laptop." > > It basically needs to be a unique for each server reboot in order > to allow clients to resynchronize. Ok, then I suggest that you cache a copy of the boottime in the NFS code for this purpose. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message