Date: Thu, 15 Nov 2007 03:04:24 -0500 From: Adam McDougall <mcdouga9@egr.msu.edu> To: Kip Macy <kip.macy@gmail.com> Cc: tss@iki.fi, freebsd-current@freebsd.org Subject: Re: link() not increasing link count on NFS server Message-ID: <20071115080424.GT37473@egr.msu.edu> In-Reply-To: <b1fa29170711142345l2cdb0f7dpd03d253599e0151e@mail.gmail.com> References: <20071115074247.GQ37473@egr.msu.edu> <b1fa29170711142345l2cdb0f7dpd03d253599e0151e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 14, 2007 at 11:45:50PM -0800, Kip Macy wrote: On Nov 14, 2007 11:42 PM, Adam McDougall <mcdouga9@egr.msu.edu> wrote: > Hi, lately I've been trying to work out some NFS multiple access issues relating > to the Dovecot IMAP server software. One symptom seems to be an unusual behavior > of FreeBSD NFS clients that I cannot reproduce with Linux or Solaris NFS clients. > Basically, Timo (cc'ed) came up with a small test case that seems to indicate > sometimes a link() call can succeed while the link count of the file will not > increase. If this is ran on two FreeBSD clients from the same NFS directory, you > will occasionally see "link() succeeded, but link count=1". I've tried both a > Netapp and a FreeBSD NFS server. I've tried FreeBSD 7_RELENG clients as well as > FreeBSD 6.2-stable from this summer. I've ran it on 32bit and 64bit clients. > I've turned rpc.lockd on and off, tried tcp vs. udp mounts, nothing so far seems > to make a difference, except perhaps FreeBSD 7.0 seems to produce the error less > often. If one of the processes is ran on a non-FreeBSD NFS cliemt, only the > FreeBSD NFS client gives the link error. Anyone have any input? Thanks. Is this with both TCP and UDP clients? We're planning on making the default TCP. -Kip Yes, I saw no difference when using TCP vs UDP.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071115080424.GT37473>