From owner-freebsd-questions@FreeBSD.ORG Mon Apr 26 11:37:19 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6E6B16A4CE for ; Mon, 26 Apr 2004 11:37:19 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D6B343D2D for ; Mon, 26 Apr 2004 11:37:19 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i3QIbHLZ004804; Mon, 26 Apr 2004 13:37:17 -0500 (CDT) (envelope-from dan) Date: Mon, 26 Apr 2004 13:37:17 -0500 From: Dan Nelson To: Tillman Hodgson Message-ID: <20040426183717.GF2771@dan.emsphone.com> References: <20040426182547.GF92049@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040426182547.GF92049@seekingfire.com> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: FreeBSD-Questions Subject: Re: NFS occassionally gives "permission" denied in the middle of a large transfer X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 18:37:19 -0000 In the last episode (Apr 26), Tillman Hodgson said: > However, this has been failing sporadically with messages like: > > > DUMP: 50.71% done, finished in 1:03 > DUMP: 53.06% done, finished in 1:01 > DUMP: 54.72% done, finished in 1:02 > gzip: stdout: Permission denied > DUMP: Broken pipe > DUMP: The ENTIRE dump is aborted. > > I've confirmed that the scripts work correctly when run by hand (and > most of the time when run from cron), that I'm not running out of > disk space, and that I'm not running out of network I/O (Athena is > Gigabit on the switch, all the other machines are 100Mbit). There > shouldn't be any concurrent access (nothing else uses this > filesystem, and each host gets it's own diretory tree) so locking > shouldn't be an issue. The only time I've seen incorrect permission denied messages is when mountd is refreshing the exports list. It's not atomic, so there's a small window where the old exports have been deleted but the new ones aren't in place yet. -- Dan Nelson dnelson@allantgroup.com