From owner-freebsd-arch Sun Mar 17 12:37: 6 2002 Delivered-To: freebsd-arch@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id B09C137B404 for ; Sun, 17 Mar 2002 12:36:59 -0800 (PST) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.6/8.11.0) id g2HKauU09320; Sun, 17 Mar 2002 15:36:56 -0500 (EST) (envelope-from jwd) Date: Sun, 17 Mar 2002 15:36:56 -0500 From: John De Boskey To: Dag-Erling Smorgrav Cc: Arch List Subject: Re: ftpd ESTALE recovery patch Message-ID: <20020317153656.A9003@bsdwins.com> References: <20020317084153.A3942@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Sun, Mar 17, 2002 at 07:57:13PM +0100 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Dag-Erling Smorgrav's Original Message ----- > John De Boskey writes: > > In a busy cluster, a generated file being handed out by > > ftp is failing due to an ESTALE condition. The following > > patch fixes the problem. Failure to open the file is also > > logged when -l is specified twice (see ftpd(8)). > > I don't see the point of this. The problem you are experiencing is > probably caused by invalid assumptions in your setup, though I can't I understand your comment, though I have to disagree with it. > comment further without more details about what, exactly, you are > trying to do. Here's a timeline: T(0) - On machine A - create new file in /tmp (/tmp/file) T(1) - On machine A - cp newfile nfsserver:/path/file.new T(2) - On machine A - mv nfsserver:/path/file.new nfsserver:/path/file T(3) - On machine B - ftp connection received get nfsserver:/path/file (get fails randomly without patch) where Time(3) is guarenteed to be greater than Time(4), though the delta between them can be approaching (but not equal to) zero. Basically, we have work nodes 1 through 28, using 2 netapp fileservers for data storage. As we continue to increase the throughput capabilities of the system, the ESTALE return happens more consistently. Ftpd is not the 1st tool we've had to fix. I hope the above helps explain in more detail the issue at hand. Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message