1.5 to 1.7 upgrade.

["Andy Hall" <fixpertise-consulting at comcast dot net>]

Slight embarrassment here.  Things are not quite as described below but
there is a problem.

1. The file systems in F: are indeed writeable, as test with echo
>builds/test demonstrated.  This is what you would expect given the
permissions shown by ls despite the question marks in the uid and gid
fields.   What is bizarre is that on one machine which is Windows 2003
Server SP2, the following happens

build@taurus /cygdrive/f
$ ls -l
total 2048
drwxrwxr-x 36 ???????? ???????? 0 2010-10-04 19:19 builds
drwxrwxr-x 17 ???????? ???????? 0 2010-10-04 18:23 releases

build@taurus /cygdrive/f
$ test -w /cygdrive/f/builds

build@taurus /cygdrive/f
$ echo $?
1

Which is why I originally thought the file system is not writeable.

On the other machine which is Windows XP Professional, you have

$ ls -l
total 2048
drwxrwxr-x 36 ???????? ???????? 0 2010-10-04 16:19 builds
drwxrwxr-x 17 ???????? ???????? 0 2010-10-04 15:23 releases

ahall@ahall-pc /cygdrive/f
$ test -w /cygdrive/f/builds

ahall@ahall-pc /cygdrive/f
$ echo $?
0

Now if I explicitly mount the remote samba share by putting the following in
/etc/fstab

//10.1.13.25/repository /repos smbfs binary,noacl 0 0

Mount produces

ahall@ahall-pc /cygdrive/f
$ mount
//10.1.13.25/repository on /repos type smbfs (binary,noacl)
C:/cygwin/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin on / type ntfs (binary,auto)
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
F: on /cygdrive/f type smbfs (binary,posix=0,user,noumount,auto)

and if I cd to /repos and do an ls, I get the following with a reasonable
uid and gid.  

ahall@ahall-pc /repos
$ ls -l
total 2048
drwxr-xr-x 36 ahall None 0 2010-10-04 16:30 builds
drwxr-xr-x 17 ahall None 0 2010-10-04 15:23 releases

Now without the explicit mounting of the directories, mount produced

$ mount
C:/cygwin/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin on / type ntfs (binary,auto)
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
F: on /cygdrive/f type smbfs (binary,posix=0,user,noumount,auto)

So the issue seems to be the difference between the use of noacl in my
explicit mount and the default one chosen by Cygwin.   How do I force the
default one to be mounted with noacl?


===========================================================================


I held off updating two machines from Cygwin 1.5 to 1.7 until this week
because they were critical to a product test and release process.  These
Cygwin installations are nearly vanilla and the upgrades went very smoothly
and except for one crucial item everything seems to have worked as expected.
Kudos to every one who contributed to this effort! 

Here's what didn't work.  Both machines map a Samba file system to the F:
drive via the normal windows mechanisms and I can read/write files in these
file system via windows.   However creating or writing files in these file
systems via Cygwin now fails whereas prior to the upgrade this was just
fine.

When I list the cygdrive directory, I get

$ ls -l
total 1024
drwxrwxr-x+ 1 Administrators SYSTEM   0 2010-10-02 02:08 c
drwxrwxr-x  4 ????????       ???????? 0 2009-10-30 08:08 f

and 

$ ls -l -n
total 1024
drwxrwxr-x+ 1        544         18 0 2010-10-02 02:08 c
drwxrwxr-x  4 4294967295 4294967295 0 2009-10-30 08:08 f

I can't remember what user / groups used to appear, but the fact that I get
the 4294967295 is clearly related to the problem.   

Mount shows

$ mount
C:/cygwin/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin on / type ntfs (binary,auto)
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
F: on /cygdrive/f type smbfs (binary,posix=0,user,noumount,auto)

which seems perfectly normal.   

The Samba version on the remote machine (Linux) is 3.0.10-1.4E.9.

Some time ago, I remember seeing e-mail in the cygwin mailing list reporting
similar issues, but I don't remember the resolution and searching has not
produced one.   

I ran the /bin/copy-user-registry-fstab script as a precaution, but this
understandably didn't do anything because I never had any mount points to
begin with. 

I don't particularly want to ask the sys admins to upgrade Samba and am
looking for a workaround.   Any help would be appreciated.

Andy Hall




--
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