Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!ubc-cs!uw-beaver!rice!cs.utexas.edu!sun-barr!olivea!uunet!spool.mu.edu!sdd.hp.com!hplabs!hpcc05!hpgva1!hpuamsa!robs
From: robs@hpuamsa.neth.hp.com (Rob Slotemaker CRC)
Newsgroups: comp.sys.hp
Subject: Re: rmdir
Message-ID: <28510021@hpuamsa.neth.hp.com>
Date: 7 Feb 91 08:09:24 GMT
References: <1991Feb06.152659.5952@ZYX.SE>
Organization: HP-Sales Office-The Netherlands
Lines: 20

As far as I can see this occurred only once before, but it was with a 9000/800
running HP-UX 3.0. The document describing that problem says :

> There appears to be a race condition between reading a directory
> (a direct read such as through ls, not a pathname lookup)
> and removing a directory.  A directory being read is not locked
> during the read.  If, after it starts reading, someone does a rmdir
> on that directory, the panic can occur.  Another way for the panic
> to occur, is for someone to rename another directory to the name of
> the directory being read.\

Does your problem occur on every rmdir of a non-empty directory ?  Are you
sure you don't have a bad disk (run fsck !) ?

Shouldn't uname -a report "HP-UX coca 7.0 B 9000/350 coca" ?


Best regards,

Rob Slotemaker, Dutch CRC