Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 16 Jun 2004 13:20:59 -0400
From: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Problem creating files on network drives with cygwin 1.5.10-3 and tar
Message-ID: <20040616172058.GA158945@Worldnet>
References: <20040616171009 DOT 97954 DOT qmail AT web61008 DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040616171009.97954.qmail@web61008.mail.yahoo.com>
User-Agent: Mutt/1.4.1i

On Wed, Jun 16, 2004 at 10:10:09AM -0700, Rick Rankin wrote:
> 
> OK, it *must* be something specific to the particular share I've been working
> with. I just mapped some other drives from other servers, tried the same tar
> command, and it worked just fine. The puzzling part is that on the problem
> share, the *only* thing that fails is tar. I can create files with touch, cp,
> vim, etc., etc. and I can remove them with rm, so it doesn't appear to be a
> permission problem. It's also not a space problem, so I'm back to building the
> debug versions...

Try writing a one line program that opens the file with flags 0x601.
That's what tar does (from your strace)
0 = fhandler_disk_file::open (m:\test.tar, 0x601)

Pierre

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/