X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 24 Aug 2010 10:36:31 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7: Basic file operations fail on network shares provided by Tru64 Advanced Server
Message-ID: <20100824083631.GN6726@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4C73712F DOT 7000801 AT dla-marbach DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4C73712F.7000801@dla-marbach.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Aug 24 09:13, Heinz Werner Kramski wrote:
> While Cygwin 1.5 played well with our legacy file server (Tru64
> Advanced Server V5.1B-4 ECO2), 1.7 does not.
> 
> Although I seem to have sufficient write permissions (and actually
> can write to files), renaming (mv-ing) files fails with 1.7.1,
> 1.7.5-1 and 1.7.6-1 (others not tested) like this:
> [...]
> With 1.7.5, it was at least possible to copy files successfully.
> After upgrading to 1.7.6-1, cp now also fails strangely:
>       $ cp somefile copyfile
>       cp: skipping file `somefile', as it was replaced while being copied

Can you please try the latest Cygwin developer snapshot at
http://cygwin.com/snapshots/, so we know this isn't fixed by the
latest bugfixes.

> Mounting with the "noacl" option doesn't help:

There's also a new mount option "ihash" since 1.7.6.  It might help
with the "cp" issue above, but that probably doesn't help with the
"mv" issue.

>       $ mv somefile newfile2
>       mv: cannot move `somefile' to `newfile2': Permission denied
> [...]
>       $ /usr/lib/csih/getVolInfo //dlanserv/KRAMSKI$/
>       Device Type        : 7
>       Characteristics    : 10
>       Volume Name        : <DLANSERV     >
>       Serial Number      : 4294967292
>       Max Filenamelength : 255
>       Filesystemname     : <NTFS>
>       Flags              : 8
>         FILE_CASE_SENSITIVE_SEARCH  : FALSE
>         FILE_CASE_PRESERVED_NAMES   : FALSE
>         FILE_UNICODE_ON_DISK        : FALSE
>         FILE_PERSISTENT_ACLS        : TRUE
>         FILE_FILE_COMPRESSION       : FALSE
>         FILE_VOLUME_QUOTAS          : FALSE
>         FILE_SUPPORTS_SPARSE_FILES  : FALSE
>         FILE_SUPPORTS_REPARSE_POINTS: FALSE
>         FILE_SUPPORTS_REMOTE_STORAGE: FALSE
>         FILE_VOLUME_IS_COMPRESSED   : FALSE
>         FILE_SUPPORTS_OBJECT_IDS    : FALSE
>         FILE_SUPPORTS_ENCRYPTION    : FALSE
>         FILE_NAMED_STREAMS          : FALSE
>         FILE_READ_ONLY_VOLUME       : FALSE
>         FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
>         FILE_SUPPORTS_TRANSACTIONS  : FALSE

These flags result in Cygwin treating the drive as a filesystem
just faking to be NTFS.  It's subsumed under the "cifs" type.
For these filesystems, just two assumptions are made:

- Don't use the FileIdBothDirectoryInformation info class in
  readdir().

- The filesystem only handles filenames following DOS rules.

However, the filesystem claims to have persistent ACLs, so the
assumption is that it has ACLs, and that it returns valid inode numbers.
Both assumptions can be overridden by mount options (noacl,ihash).

That probably still doesn't explain the "Permission denied" in case
of mv.  Would you mind to create an strace under the latest Cygwin
developer snapshot, like this:

  $ strace -o mv.trace mv somefile newfile

and send us the mv.trace file?  This might give a clue where the
problem occurs.  Maybe we can find a workaround.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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