From owner-freebsd-fs@FreeBSD.ORG Sun May 9 01:03:07 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6EEFF106566B for ; Sun, 9 May 2010 01:03:07 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 222AE8FC1D for ; Sun, 9 May 2010 01:03:06 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAN6m5UuDaFvH/2dsb2JhbACeGHG8f4J3CoIUBI9G X-IronPort-AV: E=Sophos;i="4.52,354,1270440000"; d="scan'208";a="76042589" Received: from danube.cs.uoguelph.ca ([131.104.91.199]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 08 May 2010 21:03:06 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by danube.cs.uoguelph.ca (Postfix) with ESMTP id 4D51C10842EA; Sat, 8 May 2010 21:03:06 -0400 (EDT) X-Virus-Scanned: amavisd-new at danube.cs.uoguelph.ca Received: from danube.cs.uoguelph.ca ([127.0.0.1]) by localhost (danube.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v5ShntfyQKGW; Sat, 8 May 2010 21:03:05 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by danube.cs.uoguelph.ca (Postfix) with ESMTP id E713310842DC; Sat, 8 May 2010 21:03:04 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o491HsW22951; Sat, 8 May 2010 21:17:55 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Sat, 8 May 2010 21:17:54 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Cheng-Lin Yang In-Reply-To: <1273340061.16836.yuwen@exodus.cs.ccu.edu.tw> Message-ID: References: <1272960060.34062.yuwen@exodus.cs.ccu.edu.tw> <4BDFE843.7050600@fuujingroup.com> <1273022040.28218.yuwen@exodus.cs.ccu.edu.tw> <20100505013136.GA48843@icarus.home.lan> <1273026479.56161.yuwen@exodus.cs.ccu.edu.tw> <1273340061.16836.yuwen@exodus.cs.ccu.edu.tw> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs , lab Subject: Re: Struggling on NFS problem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 May 2010 01:03:07 -0000 On Sun, 9 May 2010, Cheng-Lin Yang wrote: > Hi Rick and all, > I've upgrade the NFS server up to RELENG_8_0 with Rick's patches. I still see the negative "BioW Hits" on my FreeBSD NFS clients but the system is not hanged as before. So I would say somehow the upgrade is "partially successful" to solve the issue. > The -ve BioW value isn't particularily meaningful. For some reason, it is bogus, but it is just fyi and has no effect on the client's behaviour. (Also, note that it is a client side stat, not one for the server, so it isn't at all relevant to the server.) > Howerver, new issue bumps up after the upgrade, My mail server which runs Dovecot also mounted on NFS server, shows the following error message after the upgrade > ==== > May 8 21:46:24 mail dovecot: IMAP(USERID): fcntl(write-lock) locking failed for file cshome/professor/USERID/Maildir/.OLD2/dovecot.index.log: Operation not supported > May 8 21:46:24 mail dovecot: IMAP(USERID): mail_index_wait_lock_fd() failed with file cshome/professor/USERID/Maildir/.OLD2/dovecot.index.log: Operation not supported > May 8 21:46:24 mail dovecot: IMAP(USERID): fcntl(write-lock) locking failed for file cshome/professor/USERID/Maildir/.OLD2/dovecot.index.log: Operation not supported > May 8 21:46:24 mail dovecot: IMAP(USERID): mail_index_wait_lock_fd() failed with file /cshome/professor/USERID/Maildir/.OLD2/dovecot.index.log: Operation not supported > ==== > > Could you please kindly take a look on this new issue? Thank you. :) > If the files used by dovecot are not being concurrently accessed by other NFS clients, your best bet is to use the "nolockd" option on the mount command for dovecot. (If doevcot is a Linux client, there is a similar mount option, which I think is called "nolock" but can't remember for sure.) This option tells the client to do file locking locally in the client and imho is simpler than trying to get the Network Lock Manager working. If the files are read/write shared among multiple clients, then you'll need to try and get the Network Lock Manager (NLM) going. I don't use it (I've always thought that the protocol was poorly designed and avoided it) so I don't know much about it, but the 2 rpc servers called rpc.statd and rpc.lockd must be running on the server and the clients must be able to IP broadcast to the server. rick