From: Techie Subject: sloppy mount and lockd Date: Tue, 16 Mar 2010 11:32:39 -0700 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=QcPNsiug4tErDwsxX8ooYUuL8JvyY+JEeGb9Df+BFLE=; b=OBmMxYtJ8k/DLc5Ss3SnTiPQSZCuDiPbeMNQNoQECV1xszIK+s0mLRYgJ8dt9yuGof Dn7D6ot2Y5Sf3ZgpSiPlseScftpwWWLK+rhnAZ+YmIoCpcJWN83T8U3yBs+zG/C1pcsQ nSw3c5YuqtcbV4W+Nj6a5CYsHBRgFMV4qwyxI= List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autofs-bounces@linux.kernel.org Errors-To: autofs-bounces@linux.kernel.org To: autofs@linux.kernel.org Hi Ian, I get these in the kernel log svc: failed to register lockdv1 RPC service error no. 97 I have no idea why but using fstab does not produce these errors so just curious if they are troublesome or if you have seen this before. I have had autofs die a couple of times and wondering if its related to this in any way. Also if you have an idea why the mounts show as "sloppy" for my Autofs mounts but not fstab mounts?. I read that it is to support unrecognized options from the NFS servers such as -nobrowse. Is there a way to prevent this or can it be safely ignored? Thank you J