X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 19 Mar 2010 18:39:48 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: /cygdrive permissions problem [failing duplicity backup]
Message-ID: <20100319173948.GB17541@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4BA35384 DOT 1040100 AT frydenbo-bruvoll DOT com>  <20100319112252 DOT GL6505 AT calimero DOT vinschen DOT de>  <4BA3658D DOT 4060705 AT gmail DOT com>  <4BA36211 DOT 30109 AT frydenbo-bruvoll DOT com>  <20100319114731 DOT GO6505 AT calimero DOT vinschen DOT de>  <4BA37B3A DOT 8070901 AT frydenbo-bruvoll DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BA37B3A.8070901@frydenbo-bruvoll.com>
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 Mar 19 13:25, Jan-Aage Frydenb?-Bruvoll wrote:
>   126   56084 [main] getfacl 4280 mount_info::conv_to_win32_path: src_path /cygdrive, dst D:\cygwin\cygdrive, flags 0x3000A, rc 0

That's what puzzles me a lot.  The cygdrive prefix should never have been
converted to a valid Win32 path.  Not according to your mount 


>   113   56197 [main] getfacl 4280 build_fh_pc: fh 0x6120DF7C
>   111   56308 [main] getfacl 4280 stat_worker: (\??\D:\cygwin\cygdrive, 0x22CCC8, 0x6120DF7C), file_attributes 17
>    91   56399 [main] getfacl 4280 fhandler_base::fstat: here
>  4717   61116 [main] getfacl 4280 stat_worker: 0 = (\??\D:\cygwin\cygdrive, 0x22CCC8)
>   120   61236 [main] getfacl 4280 normalize_posix_path: src /cygdrive/
>    85   61321 [main] getfacl 4280 normalize_posix_path: /cygdrive/ = normalize_posix_path (/cygdrive/)
>    84   61405 [main] getfacl 4280 mount_info::conv_to_win32_path: conv_to_win32_path (/cygdrive)
>    84   61489 [main] getfacl 4280 set_flags: flags: binary (0x2)
>    83   61572 [main] getfacl 4280 mount_info::conv_to_win32_path: src_path /cygdrive, dst D:\cygwin\cygdrive, flags 0x3000A, rc 0
>    86   61658 [main] getfacl 4280 build_fh_pc: fh 0x6120DF7C

At this point something goes wrong, but unfortunately it's not clear
from the strace output what that is.  The created file handler is one
for disk-based files, rather than a cygdrive handler.

>   529   62187 [main] getfacl 4280 fhandler_base::set_flags: flags 0x110000, supplied_bin 0x0
>    99   62286 [main] getfacl 4280 fhandler_base::set_flags: O_TEXT/O_BINARY set in flags 0x10000
>    98   62384 [main] getfacl 4280 fhandler_base::set_flags: filemode set to binary
>    95   62479 [main] getfacl 4280 fhandler_base::fstat_by_handle: 0xC0000008 = NtQueryInformationFile(\??\D:\cygwin\cygdrive, FileBasicInformation)

This is bad as well.  If your directory D:\cygwin\cygdrive really exists,
you shouldn't see such an error (STATUS_INVALID_HANDLE).  Very strange.

> c:  hd  NTFS    118950Mb  78% CP CS UN PA FC     Data
> d:  hd  NTFS     71782Mb  82% CP CS UN PA FC     
> e:  cd             N/A    N/A                    
> f:  cd             N/A    N/A                    
> g:  fd  FAT       1914Mb   9% CP    UN           Memory card
> 
> D:\cygwin        /          system  binary,auto
> D:\cygwin\bin    /usr/bin   system  binary,auto
> D:\cygwin\lib    /usr/lib   system  binary,auto
> cygdrive prefix  /cygdrive  user    binary,auto

This looks insuspicious.
> 
> Potential app conflicts:
> 
> Logitech Process Monitor service
> Detected: HKLM Registry Key, Named process.

This might be the problem, but I have no own experience with the potential
problems arising from using these tools.


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