RE: 1.5.25: "changed dev/ino" error with shared drives

["Correa, Wagner" <Wagner dot Correa at gs dot com>]

>-----Original Message-----
>From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] 
>On Behalf Of Dave Korn
>Sent: Sunday, February 08, 2009 4:23 PM
>To: cygwin@cygwin.com
>Subject: Re: 1.5.25: "changed dev/ino" error with shared drives
>
>Larry Hall (Cygwin) wrote:
>> Correa, Wagner wrote:
>>>> Correa, Wagner wrote:
>>>>> I'm using Cygwin 1.5.25, and when I try removing 
>>>> directories in shared
>>>>> drives, I get an error message like this:
>>>>>
>>>>> rm: FATAL: directory `foo' changed dev/ino
>>>>>
>>>>> Could this be a reoccurrence of this old problem?
>>>>> http://www.cygwin.com/ml/cygwin/2006-02/msg00315.html.
>>>> Given the different format of the message and the abundance of 
>>>> alternate but like-named tools on your machine, I have to 
>wonder if 
>>>> you're getting this message from Cygwin's 'rm'.
>
>   If you run strings on Cygwin's /bin/rm, you'll see it uses 
>the exact same 
>message these days.
>
>>>>  Are you?
>
>   That notwithstanding, it would be a very good idea to clean 
>out the PATH so 
>that only one set of unix tools are in play at a time.  I 
>stopped counting at 
>about six or seven differing and potentially incompatible toolsets 
>simultaneously available...
>
>>> I think so:
>>> $ which rm
>>> /usr/bin/rm
>>>
>>> But how can I be sure?
>> 
>> Invoke '/usr/bin/rm' directly.  If you still see a problem, we need
>> to see the permissions of the directory you're working with ('ls -l'
>> and 'getfacl') and its contents as well as the input and results you
>> get.  Perhaps stracing might be necessary as well but I'll hold off
>> asking for that right now.  Let's see if the above helps you find the
>> problem.
>
>   What would also be interesting would be to see the 
>getvolinfo output for 
>the drive(s) in question.  Wagner, if you run these two commands:
>
>wget 'http://tinyurl.com/cygwin-getvolinfo' -O getVolInfo.c
>gcc getVolInfo.c -lntdll -o getVolInfo
>
>and then "./getVolInfo Z:" - or whichever network drive 
>letter(s) give you the 
>problem - we'll know more about how you're connected.  (Is it 
>a NetApp?)
>
>[ FYI, and as the wget output would show you anyway, the 
>tinyurl leads to
>http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/csih/cygwin
/getVolInfo.c?cvsroot=cygwin-apps 
>but I figured that was likely to get wrapped... ]
>
>     cheers,
>       DaveK
>
>
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Problem reports:       http://cygwin.com/problems.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/
>

Hi, Dave!

I just tried it again with a cleaner PATH, but I still got the same
problem. I'm attaching the cygcheck.out for this cleaner PATH.

Here is the result of running getVolInfo:
$ ./getVolInfo Z:
Device Type        : 7
Characteristics    : 10
Volume Name        : <correw>
Serial Number      : 3758342752
Max Filenamelength : 255
Filesystemname     : <NTFS>
Flags              : 4000f
  FILE_CASE_SENSITIVE_SEARCH  : TRUE
  FILE_CASE_PRESERVED_NAMES   : TRUE
  FILE_UNICODE_ON_DISK        : TRUE
  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          : TRUE
  FILE_READ_ONLY_VOLUME       : FALSE
  FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
  FILE_SUPPORTS_TRANSACTIONS  : FALSE

How can I tell if it is a NetApp?

Thanks,

Wagner

Attachment: cygcheck.out
Description: cygcheck.out

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