public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cgf@bbc.com (Chris Faylor)
To: gnu-win32@cygnus.com
Subject: Re: interesting problem with "find"
Date: Tue, 11 Nov 1997 16:20:00 -0000	[thread overview]
Message-ID: <EJI572.66C@bbc.com> (raw)
In-Reply-To: <346874E8.571D@switch.rockwell.com>

In article < 346874E8.571D@switch.rockwell.com >,
Bartlee A. Anderson <banders@ECD.Rockwell.COM> wrote:
>I've noticed a similar problem with rm.
>In directories with structure something/yada/yada/other/...
>rm -rf will tell you that you have a circular directory structure and to
>notify your administrator, it is almost certainly corrupt.
>You have to remove from the second yada and then once it's gone, the
>original command will work. Yuck.

I don't think that this is a problem with your directory.  More likely,
this is a problem with cygwin's calculation of inodes.  rm -rf keeps
track of the inodes of directories that it deletes.  If it comes across
a directory with the same inode as one it thinks that it has already deleted,
then it thinks something is wrong.

Since Windows does not support the concept of an inode, cygwin has to
create its own.  It bases the inode on the name of the file.  So, if you
have two directories with the same name, they'll have the same inode.
When rm -r sees these two (different) directories with the same inode,
it complains.

Currently, the only workaround is to delete the lower level subdirectories
by hand.  Sorry.
-- 
http://www.bbc.com/	cgf@bbc.com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  reply	other threads:[~1997-11-11 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-10 14:03 Alan
1997-11-11  7:07 ` Bartlee A. Anderson
1997-11-11 16:20   ` Chris Faylor [this message]
1997-11-11 11:13 Larry Hall (RFK Partners Inc)
1997-11-11 20:57 ` Fergus Henderson
1997-11-12  3:35 ` Geoffrey Noer
1997-11-12 15:49 raf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EJI572.66C@bbc.com \
    --to=cgf@bbc.com \
    --cc=gnu-win32@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).