X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <498F4D29.8060309@gmail.com> Date: Sun, 08 Feb 2009 21:22:49 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.5.25: "changed dev/ino" error with shared drives References: <9B4F9A0AAE2F3A48899500BE7128667503C2D359 AT gsmbcdp40es DOT firmwide DOT corp DOT gs DOT com> <498E1703 DOT 4050800 AT cygwin DOT com> <9B4F9A0AAE2F3A48899500BE7128667503C2D35B AT gsmbcdp40es DOT firmwide DOT corp DOT gs DOT com> <498F3606 DOT 2090800 AT cygwin DOT com> In-Reply-To: <498F3606.2090800@cygwin.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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/