From owner-freebsd-fs@FreeBSD.ORG Sun Jun 2 12:30:52 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3AE68A38 for ; Sun, 2 Jun 2013 12:30:52 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 0349610FE for ; Sun, 2 Jun 2013 12:30:51 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAK85q1GDaFvO/2dsb2JhbABahnW7RIESdIIjAQEFI1AGGw4KAgINGQJZBhOIDah9kQaBJo1NNAeCRIEUA5c+kUCDKyCBaw X-IronPort-AV: E=Sophos;i="4.87,788,1363147200"; d="scan'208";a="32364924" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 02 Jun 2013 08:29:43 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 50ECEB4045; Sun, 2 Jun 2013 08:29:43 -0400 (EDT) Date: Sun, 2 Jun 2013 08:29:43 -0400 (EDT) From: Rick Macklem To: Dmitry Morozovsky Message-ID: <1781152855.121926.1370176183284.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: NFS+ZFS+nullfs on Server random Permission Denied errors on client (nfsv4) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org, Bryan Drewery X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jun 2013 12:30:52 -0000 Dmitry Morozovsky wrote: > On Wed, 29 May 2013, Rick Macklem wrote: > > > Bryan Drewery wrote: > > > Server: > > [snip] > > > > Problem: > > > > > > For months I constantly get random Permission Denied errors on the > > > client side. Just trying the read again can fix the problem. The > > > client > > > will usually show this in dmesg as the same time: > > > > nfsv4 client/server protocol prob err=10020 > > > > > This error means "no file handle" and I believe it will happen when > > the client tries to access the root of the exported tree. (The root > > specified by the "V4: ..." line in /etc/exports.) > > Isn't it the problem with mountd cleaning all exports and re-exporting > new list > on every mount(2) call? > Yes, good point. Doing mounts or sending HUP to mountd could certainly cause this. (Back when I used a FreeBSD system as a production NFS server, I never did mounts on it or changed the /etc/exports, I just configured it and let it run for mounts/years, so I tend to forget this issue.;-) If this is the cause and you have a recent enough system to support it, you can try the "-S" option on mountd. Alternately, this issue can be avoided by switching from mountd to nfse (found on sourceforge). rick > > -- > Sincerely, > D.Marck [DM5020, MCK-RIPE, DM3-RIPN] > [ FreeBSD committer: marck@FreeBSD.org ] > ------------------------------------------------------------------------ > *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru > *** > ------------------------------------------------------------------------