Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucla-cs!ucivax!jarthur!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!mcsun!ukc!mucs!cns!umaida!rn
From: rn@ap.co.umist.ac.uk (bob nutter)
Newsgroups: comp.sys.apollo
Subject: Problem accessing file
Message-ID: <1991Feb27.162855@ap.co.umist.ac.uk>
Date: 27 Feb 91 16:28:55 GMT
Sender: news@cns.umist.ac.uk (Usenet news)
Reply-To: rn@ap.co.umist.ac.uk (bob nutter)
Organization: UMIST Computation dept, Manchester, UK
Lines: 19

Hi!

I started this post out as a plea to help me delete a file that *had* an
inode, but would only allow ls and ls -i on it. No rm, find or ls -l would
touch it, they *all* hung and devoured CPU time (great on cron'd find and du
scripts! *;^). I was also about to bemoan the lack of clri(8),icheck(8) and
fsck(8), then I remembered /com/dlf, which worked first time. Should I have
run syncids or something? Can anyone explain why an innocent little file
(somebody's ~/user_data/key_defs3) should suddenly go arse-over-tit like this
and apparently lose it's connection between it's Domain id and it's unix id???
This is at sr10.1, BTW.

bob
-------------------------------------------------------------------------------
bob nutter, computer officer    | "That's a good example to your children,
UMIST dept of computation       |  lying on national TV!" 
po box 88 manchester m60 1qd uk |    -Jello Biafra talking to Tipper Gore
tel:+44 61 200 3386             |     on Oprah Winfrey 
email:b.nutter@umist.ac.uk      |