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] |
Dear Cygwin folks, I have a showstopper problem with Cygwin 1.7: it just does not want to work with some of my Samba shares. The shares lie on a pretty old linux samba server (smbd 3.0.17) but I have no control over it, so I cannot just replace it. Cygwin 1.5 had no trouble with these shares, just like all Windows programs, but starting with Cygwin 1.7, most directories and all files become inaccessible. Here is what I get: $ ls -l '\\HERA\shared\benchmarks\test' ls: cannot access \\hera\shared\benchmarks\test: Not a directory The DOS equivalent works as it should: $ cmd /c DIR '\\HERA\shared\benchmarks\test' ?Volume in drive \\hera\shared is shared ?Volume Serial Number is 0262-0867 ?Directory of \\hera\shared\benchmarks\test 2010-03-02? 19:45??? <DIR>????????? . 2010-03-02? 10:18??? <DIR>????????? .. 2010-03-02? 10:20??????????????? 42 README.txt ?????????????? 1 File(s)???????????? 42 bytes ???? ??????????2 Dir(s)???? 648?019?968 bytes free Now (after using the DOS command), ls will list the file names but nothing more: $ ls -l '\\HERA\shared\benchmarks\test' ls: cannot access \\hera\shared\benchmarks\test/README.txt: No such file or directory total 0 -????????? ? ? ? ???????????????? ? README.txt $ It does not matter if I am writing the name with slashes or backslashes or using DOS drive letter or Cygwin mount name, the results are the same. The getVolCheck output seems normal to me: $?? /lib/csih/getVolInfo? '//HERA/shared' Device Type??????? : 7 Characteristics??? : 10 Volume Name??????? : <shared> Serial Number????? : 39979111 Max Filenamelength : 255 Filesystemname???? : <NTFS> Flags????????????? : b ? FILE_CASE_SENSITIVE_SEARCH? : TRUE ? FILE_CASE_PRESERVED_NAMES?? : TRUE ? 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 I do not quite understand what is going on; doesn't Cygwin uses Windows standard calls to access the network drives? If not, can it back up to the Windows calls when its own methods fail? Any help appreciated -- Ilya Beylin????? ?
Attachment:
cygcheck.out
Description: cygcheck.out
-- 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] |