Date: Thu, 15 Jul 1999 04:30:02 -0700 (PDT) From: Jan Conrad <conrad@th.physik.uni-bonn.de> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/12609: At boottime NFS mounts on a 3.2 client from a 2.2.7 server fails, when in turn the server has NFS mounted filesystems on the client Message-ID: <199907151130.EAA67225@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/12609; it has been noted by GNATS.
From: Jan Conrad <conrad@th.physik.uni-bonn.de>
To: freebsd-gnats-submit@freebsd.org, conrad@th.physik.uni-bonn.de
Cc:
Subject: Re: kern/12609: At boottime NFS mounts on a 3.2 client from a 2.2.7
server fails, when in turn the server has NFS mounted filesystems on the
client
Date: Thu, 15 Jul 1999 13:28:38 +0200 (CEST)
Hi again,
The problem is due to the use of realpath in mountd. Realpath in turn uses
getcwd, the 'canonical' part of which lstats some directory entries when
looking at a parent directory of a mount point.
If now two NFS mountpoints are in the same directory and the one first in
the directory is down for some reason, a getcwd somewhere in the second
one will block till the first one is up again.
However, mountd uses realpath to check the mountpoint, therefore it will
not mount it until the first one is up again......
Anyhow - I think this causes some NFS lookups, even if not by mountd....
Dirty Workaround:
hide all NFS mountpoints for one machine in a single dir (e.g.
/mount/machine/dir) and then symlink to it..
Better:
Rewrite getcwd (Is there no syscall to find out the device of a
mountpoint without doing a stat on it??)
(I am gonna ask this on freebsd-hackers)
best regards
Jan
--
Physikalisches Institut der Universitaet Bonn
Nussallee 12
D-53115 Bonn
GERMANY
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907151130.EAA67225>