Date: Sat, 24 Aug 2002 10:07:36 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Nate Lawson <njl@FreeBSD.ORG> Cc: njl@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: kern/41216: Get "NFS append race" error Message-ID: <200208241707.g7OH7aPj013422@apollo.backplane.com> References: <200208240102.g7O12eeL087425@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:Synopsis: Get "NFS append race" error : :Responsible-Changed-From-To: freebsd-bugs->dillon :Responsible-Changed-By: njl :Responsible-Changed-When: Fri Aug 23 17:59:59 PDT 2002 :Responsible-Changed-Why: :The code recovers from the race by updating the dirty end pointer to what :it should be. It may be difficult to prevent the race from occurring due :to bio locking complexities. Over to dillon to see if he wants to comment :or just punt. : :http://www.freebsd.org/cgi/query-pr.cgi?pr=41216 This is a long standing problem which I still haven't tracked down. As long as only one NFS client host is doing the appending this case is not supposed to occur at all because the vnode should be locked through the nfs_write() operation. Apparently the case does still occur though and I am not sure why. This is why the printf() is still in there. If multiple client hosts are appending to the same file then the case can definitely occur (it's a problem with the NFSv2/v3 protocol itself that is not fixable). -Matt Matthew Dillon <dillon@backplane.com> 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?200208241707.g7OH7aPj013422>