Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 85246 invoked from network); 28 Jul 2009 18:03:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Jul 2009 18:03:16 -0000 Received: (qmail 82324 invoked by uid 500); 28 Jul 2009 18:04:32 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 82232 invoked by uid 500); 28 Jul 2009 18:04:32 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 82222 invoked by uid 99); 28 Jul 2009 18:04:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jul 2009 18:04:32 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of groodt@gmail.com designates 209.85.218.211 as permitted sender) Received: from [209.85.218.211] (HELO mail-bw0-f211.google.com) (209.85.218.211) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jul 2009 18:04:24 +0000 Received: by bwz7 with SMTP id 7so215148bwz.28 for ; Tue, 28 Jul 2009 11:04:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=1KSSMwz/HqG3Hpzhs08Xi3H4yv//X1WmEtu0GC2HGds=; b=RGZbHmhaLjVV+PvHvftLMBWjSjzP4nOp2QVUH+90RBU6w9QSPLxBJ5ZkzFp/ODLzYg R6gt7/X+5YPJLjnplY3kVNfYUO5qTwz6d/RnLmGzGK5tsq0ZBv9133kGJNoWLEvzPdDA nRevvwaUkvL6xdHgrl4yeJCl82FiWQvfHUZzs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=cW+bR6pi/rsafFiFuhMDnnPoxlz0qeSyqwWiRdxG+wD9b2k9T6VUlHymNl3MEc14o3 PIBtfYYlme/AV1UF7FaBndraACx9O48QuGu3UJSJFLUYaf+Y838awR66E65ZSDVqy5nK aIfFvr/Q+8KLNDVtBI5NUY3f9LZm8ReqbkSJg= MIME-Version: 1.0 Received: by 10.223.113.68 with SMTP id z4mr3692283fap.72.1248804242579; Tue, 28 Jul 2009 11:04:02 -0700 (PDT) In-Reply-To: References: Date: Tue, 28 Jul 2009 19:04:02 +0100 Message-ID: <519c1a0c0907281104j22d31bcdxf21a329e0d7ecb56@mail.gmail.com> Subject: Re: Problem with zip task From: Greg Roodt To: Ant Users List Content-Type: multipart/alternative; boundary=00504502b19445e50c046fc7e5d3 X-Virus-Checked: Checked by ClamAV on apache.org --00504502b19445e50c046fc7e5d3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hmmmm, looks a bit suspicious. Could you please include the relevant parts of the build.xml? I know that a few Java File operations dont work very well across file systems. Renaming has given me problems in the past. On Tue, Jul 28, 2009 at 6:58 PM, Cole, Derek E wrote: > The mounts are persistent, and we are not doing anything like that as > part of the build. > > > I did find some information on the .nfs files: > > > .nfs files are created by a clienthost when one process on the > clienthost deletes a file while another process on the clienthost is > still holding the file open. This allows the delete to appear to > succeed for one process w/o causing the the process to begin getting > stale nfs file handles. It is a hack, but it is the only way to > simulate UFS semantics on NFS. The clienthost will normally delete the > .nfs file once the remaining process holding the file open closes > it. However, if the clienthost crashes, you get left with a .nfs file > on the filer. > > > Note that if more than one host is involved (e.g, process on host a is > holding a file open over NFS, while process on host b deletes that > over NFS), process a will get a stale file handle. > > > Could something like this be happening as part of a simple zip task? > > > -----Original Message----- > From: Scot P. Floess [mailto:sfloess@nc.rr.com] > Sent: Tuesday, July 28, 2009 1:56 PM > To: Ant Users List > Subject: Re: Problem with zip task > > > Interesting looks like an nfs issue... Are you automounting or > anything? > > On Tue, 28 Jul 2009, Cole, Derek E wrote: > > > Has anyone encountered a problem when running a zip task, the log will > > say something like > > > > [zip] Building zip: /path-to/some.war > > > > [zip] adding directory ........ > > > > > > > > Then getting an exception that says > > > > > > > > Problem creating zip: > > /path-to/someotherdir/.nfs0000000000000001a121a00000003ae (No such > file > > or directory) > > > > > > > > > > > > The way the problem is listed..doesnt that seem like a problem with a > > network storage access? /path-to/ is a mount to a NAS > > > > > > Scot P. Floess > 27 Lake Royale > Louisburg, NC 27549 > > 252-478-8087 (Home) > 919-890-8117 (Work) > > Chief Architect JPlate http://sourceforge.net/projects/jplate > Chief Architect JavaPIM http://sourceforge.net/projects/javapim > > Architect Keros http://sourceforge.net/projects/keros > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org > For additional commands, e-mail: user-help@ant.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org > For additional commands, e-mail: user-help@ant.apache.org > > --00504502b19445e50c046fc7e5d3--