From owner-freebsd-hackers Mon Apr 10 13:39:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 38F7937B647 for ; Mon, 10 Apr 2000 13:39:30 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA32367 for ; Mon, 10 Apr 2000 16:39:29 -0400 (EDT) Message-Id: <200004102039.QAA32367@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: NFS FHs, what are they (how are they made?) Date: Mon, 10 Apr 2000 16:39:28 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was previously under the impression that a NFS FH was basically a concatenation of a device # and an inode #. This was shot down earlier today. The problem was that a disk had failed and we where doing a replacement (the new disk was not identical to the old, it was substantially larger). I proceeded to format it so that the old fstab entry would work with the new drive (that is the NFS exported partition would be called /dev/wd1s1h -- same device number, no?) I then used dump/restore to ensure that the inode numbers would remain the same. Making to further changes I shut down the machine, swapped in the new drive and brought the system back up. 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? -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message