Date: Wed, 26 Aug 1998 02:10:47 -0400 (EDT) From: "John W. DeBoskey" <jwd@unx.sas.com> To: freebsd-current@FreeBSD.ORG Subject: ESTALE on nfs mount point(HELP!) Message-ID: <199808260610.AA02989@mozart>
next in thread | raw e-mail | index | archive | help
Hi, The following is occurring on a machine running 3.0-980506-SNAP. I don't have any 2.x machines to replicate this problem with. Given the following situation, how can I unmount an nfs filesystem that the system doesn't think is mounted (unless I try to mount it)??? If I reboot the machine having this problem than everything will work correctly (until it fails again). Note: 'afsserver' is runnning an AFS/NFS translator. # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 254063 20499 213239 9% / /dev/wd0s1g 4546645 521967 3660947 12% /usr /dev/wd0s1e 254063 3495 230243 1% /var procfs 4 4 0 100% /proc /dev/ccd0c 40370268 20696354 16444293 56% /hpdisk server01:/home/ss1 151811856 87502404 64309452 58% /ss1 amd:131 0 0 0 100% /u amd:131 0 0 0 100% /nfs Note: df doesn't show the filesystem as mounted. # mount afsserver:/afs /afs mount: /afs: Stale NFS file handle # umount -vf /afs /afs: unmount from afsserver:/afs umount: afsserver:/afs: No such file or directory # rmdir /afs rmdir: /afs: Device busy # showmount -e afsserver Exports list on afsserver: /afs Everyone /local Everyone / Everyone # /afs is normally mounted via the fstab file. Any accesses to /afs in it's current condition return ESTALE. So, how can I fix this problem without a reboot? For what its worth, an 'ls /nfs/afsserver/afs' automounts correctly and works. Unfortunately, I can't use that mount point (don't ask why). Any pointers are greatly appreciated. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808260610.AA02989>