This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Permission Problems


On Mon, Apr 25, 2016 at 12:09 AM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
> On 25/04/2016 02:29, Dave Caswell wrote:
>>
>> This is a followup to: https://cygwin.com/ml/cygwin/2016-03/msg00345.html
>>
>> To recap, making three nested directories  on a non-C drive produces a
>> third level which is unusable.
>>
>> davec@MERCURYWIN ~/python
>> $ rm -rf g1
>> davec@MERCURYWIN ~/python
>> $ mkdir g1 g1/g2 g1/g2/g3
>> davec@MERCURYWIN ~/python
>> $ ls -la g1 g1/g2 g1/g2/g3
>> g1:
>> total 12
>> drwxrwxr-x+ 1 davec None 0 Mar 16 20:23 ./
>> drwxrwx---+ 1 davec Users 0 Mar 16 20:23 ../
>> drwsrwsr-t+ 1 davec None 0 Mar 16 20:23 g2/
>> g1/g2:
>> total 0
>> drwsrwsr-t+ 1 davec None 0 Mar 16 20:23 ./
>> drwxrwxr-x+ 1 davec None 0 Mar 16 20:23 ../
>> d--Srws--T+ 1 davec None 0 Mar 16 20:23 g3/
>> ls: cannot open directory 'g1/g2/g3': Permission denied
>>
>> The problem went away with Cygwin 2.5.0-0.7 but is back with 2.5.1-1,
>> and goes away when I downgrade back to 2.5.0-1
>>
>> More info:  I tested on a couple of external drives and things worked
>> properly there.   Can I have screwed up the permissions on my D drive
>> so that cygwin gets confused but Windows still works?
>>
>> thanks
>
>
> It works fine for me.
> "E:" is an external NTFS USB disk
>
> $ mount
> E:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
> E:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
> E:/cygwin64 on / type ntfs (binary,auto)
> C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
> E: on /cygdrive/e type ntfs (binary,posix=0,user,noumount,auto)
>
>  $ cd /cygdrive/e/temp
>
>  $ mkdir g1 g1/g2 g1/g2/g3
>
>  $ ls -la g1 g1/g2 g1/g2/g3
> g1:
> total 4.0K
> drwxr-xr-x+ 1 marco Administrators 0 Apr 25 07:59 .
> drwxr-xr-x+ 1 marco Administrators 0 Apr 25 07:59 ..
> drwxr-xr-x+ 1 marco Administrators 0 Apr 25 07:59 g2
>
> g1/g2:
> total 0
> drwxr-xr-x+ 1 marco Administrators 0 Apr 25 07:59 .
> drwxr-xr-x+ 1 marco Administrators 0 Apr 25 07:59 ..
> drwxr-xr-x+ 1 marco Administrators 0 Apr 25 07:59 g3
>
> g1/g2/g3:
> total 0
> drwxr-xr-x+ 1 marco Administrators 0 Apr 25 07:59 .
> drwxr-xr-x+ 1 marco Administrators 0 Apr 25 07:59 ..
>
>  $ icacls .
> . GE-MATZERI-EU\0356EU:(F)
>   BUILTIN\Administrators:(RX)
>   Everyone:(RX)
>   NT AUTHORITY\SYSTEM:(OI)(CI)(F)
>   CREATOR OWNER:(OI)(CI)(IO)(F)
>   CREATOR GROUP:(OI)(CI)(IO)(RX)
>   Everyone:(OI)(CI)(IO)(RX)
>
> $ icacls g1/g2/g3
> g1/g2/g3 NULL SID:(DENY)(Rc,S,REA,X,DC)
>          GE-MATZERI-EU\0356EU:(F)
>          BUILTIN\Administrators:(RX)
>          NT AUTHORITY\SYSTEM:(RX,W,DC)
>          Everyone:(RX)
>          NULL SID:(OI)(CI)(IO)(DENY)(Rc,S,REA,X,DC)
>          CREATOR OWNER:(OI)(CI)(IO)(F)
>          CREATOR GROUP:(OI)(CI)(IO)(RX)
>          NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(RX,W,DC)
>          Everyone:(OI)(CI)(IO)(RX)
>
> I suggest to use icacls and eventually "setfacl -b"
> for permission cleaning if needed.

What wound up doing was backing up all the files from my documents
disk to a scratch disk, reformatting the documents disk, and restoring
the backup, and finally running icacls /reset on the whole drive.
This seems to have my system working ok now.

But there is still something different about 2.5.0-1 that prevented it
from writing a confused ACL.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]