From owner-freebsd-hackers Mon Apr 10 18:26:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id C9BE037B556 for ; Mon, 10 Apr 2000 18:26:44 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id KAA83907; Tue, 11 Apr 2000 10:57:12 +0930 (CST) (envelope-from newton) Date: Tue, 11 Apr 2000 10:57:12 +0930 From: Mark Newton To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS FHs, what are they (how are they made?) Message-ID: <20000411105712.B83822@internode.com.au> References: <200004102039.QAA32367@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200004102039.QAA32367@cs.rpi.edu> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 10, 2000 at 04:39:28PM -0400, David E. Cross wrote: > The new drive was mounted faithfully by the old fstab. Yet I now see > "Stale NFS Handle"s on my clients. What did I do wrong? restore(8) doesn't preserve inode allocations: A level zero dump must be done after a full restore. Because restore runs in user code, it has no control over inode allocation; thus a full dump must be done to get a new set of directories reflecting the new in- ode numbering, even though the contents of the files is unchanged. I believe FH numbering is a bit more complicated than dev/inode concatenation anyway, but the lack of inode number preservation is probably what bit you this time. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message