From owner-freebsd-hackers Sun May 7 23:44:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3E2BF37B5C4 for ; Sun, 7 May 2000 23:44:16 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA14811; Sun, 7 May 2000 23:44:13 -0700 (PDT) (envelope-from dillon) Date: Sun, 7 May 2000 23:44:13 -0700 (PDT) From: Matthew Dillon Message-Id: <200005080644.XAA14811@apollo.backplane.com> To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: One NFS cookie question References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have one question regarding the usage of NFS cookies. I read the :following passage in the mailing list archive: : :-------- : :The BSD code simpy re-reads all of the directory blocks until it :hits the right offset again whenever it gets NFSERR_BAD_COOKIE. However, :suppose you have a directory of 3 blocks. You read the first block. :Your offset is now at the end of the first block. You delete all the :files in the first block. You want to read the 2nd block. You get :BAD_COOKIE. So then you start again from the beginning, until you :are at the wanted offset. However, the first block has disappeared now, :so your offset lands you at what was originally the 3rd block. You've :missed the 2nd block entirely. : :------- : :Is this problem solved or not in FreeBSD 4.0-Release? : :-Zhihui I think this problem has been solved, at least insofar as Solaris clients (which are sensitive to BAD_COOKIE returns from a FreeBSD NFS server) are concerned . -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message