Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!bu-cs!purdue!decwrl!hplabs!sdcrdcf!trwrb!scgvaxd!wlbr!etn-rad!markus
From: markus@etn-rad.UUCP (Markus Richardson)
Newsgroups: comp.bugs.sys5
Subject: /etc/link problem via /etc/mvdir
Message-ID: <532@etn-rad.UUCP>
Date: 21 May 88 01:23:35 GMT
Organization: Eaton Inc. IMSD, Westlake Village, CA
Lines: 24

I did something dangerous/stupid but only realized it after the fact.  
(I'm sure I've heard that one before :-)
my . directory looked something like:
	dir1/  dir2/  dir3/  dir4/  dir5/  dir6/  dir7/  dir8/  dir9/

I entered '/etc/mvdir * dir9' thinking (ala /bin/mv) that /etc/mvdir
and /etc/link would be smart enough to catch that I was trying to
link a directory (namely dir9) to itself.  Well, after no error message I 
got alittle panicky and of course did a /bin/ls.  Nothing in the . directory!

Needless to say, I could not locate the directories and associated files
until I did a /etc/fsck.  They all turned out to be UNREFerenced.  What the 
heck happened?   If it matters, I am running SysV.2 on a Plexus.

-- 

        Markus N. Richardson
        Research and Development
        Eaton Corporation IMSD
        31717 La Tienda Drive
        Westlake Village, CA 91359
        
        { voder,ihnp4,trwrb,scgvaxd,jplgodo }!wlbr!etn-rad!markus
          wlbr!etn-rad!markus@etn-wlv.eaton.com