Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!snorkelwacker!ira.uka.de!rusux1!jellosub.luftfahrt.uni-stuttgart.de!schmid
From: schmid@jellosub.luftfahrt.uni-stuttgart.de (Georg Schmid)
Newsgroups: comp.sys.apollo
Subject: Re: more 'failing update SR10.1.p->SR10.2.p'
Keywords: SR10.2.p
Message-ID: <187@rusux1.rus.uni-stuttgart.de>
Date: 11 Jul 90 07:14:02 GMT
References: <185@rusux1.rus.uni-stuttgart.de> <186@rusux1.rus.uni-stuttgart.de> <1990Jul10.195225.24128@terminator.cc.umich.edu>
Sender: zrf80385@rusux1.rus.uni-stuttgart.de
Reply-To: schmid@jellosub.luftfahrt.uni-stuttgart.de (Georg Schmid)
Organization: Institut fuer Statik & Dynamik der Luft- und Raumfahrtkonstruktionen
Lines: 63

In article <1990Jul10.195225.24128@terminator.cc.umich.edu>,
rees@citi.umich.edu (Jim Rees) writes,

> In article <186@rusux1.rus.uni-stuttgart.de>,
> schmid@asterix.luftfahrt.uni-stuttgart.de (Georg Schmid) writes:
>    So what I do now at the beginning of 
>    rc.local is: 
>       /bin/rm -rf /sys/node_data/systmp
>       /bin/mkdir /sys/node_data/systmp
>
> I still think it's a bad idea to do this in rc.local.  I would personally
> not try it except just before shutdown.  If you find it necessary to do this
> on every boot, then something else is seriously broken and you should try to
> track it down and fix it.
>
> If you need an immediate workaround, I would try instead:
>       /bin/rm -f /sys/node_data/systmp/tcp_data

Well, I tried to rm /sys/node_data/systmp/tcp_data already (in fact this
was one of my very first experiments) but that didn't help, on the contrary
this seemed to make the node hanging for sure.

When I looked at the /sys/node_data directory in the Autorized Area, I saw
that there is no template for systmp, so this means, the time when 
systmp is created for the first time, has to be at boot time.

I couldn't figure out where this is done for nodes with disks, but for
diskless nodes it's done in /sys/net/netman.bin_sh.

When you look at that file, you can see that for diskless nodes the 
following happens:

 - When /sys/node_data.<diskless_node_id>/systmp doesen't exist on the 
   partner node, the directory systmp will be created with mode 777.
 - If systmp does exist, the directory (and its contents) will be
   unlocked by /etc/ulkob -f 

When I tried to fix the problem using /etc/ulkob, the node hung again.

For all that, up to my opinion it should be absolutely legal to remove
systmp and to recreate it with mode 777. 

The reason why I do this at the beginning of rc.local (perhaps there
might be some nicer/earlier place) is, that I want it to be done 
automatically on every boot. This is necessary because some guys work 
with I-DEAS and Domain Phigs on that machine, and it ist rather 
unpredictable when the next 'shutdown' will happen.

After all I'm happy with it working this way, and I don't know how to
track down the error further (I already spent a lot of time waiting for
salvol to complete). 
I do think that there is something seriously broken but I also think it's 
not my job to fix it, its the job of HP/Apollo. (The machine was 
installed completley new, including invol etc. so I guess it's not my
fault that it didn't work)

Thanks to all who helped me with their hints.
 
-----
Georg Schmid, ISD University of  Stuttgart, W.-Germany     
email: schmid@asterix.luftfahrt.uni-stuttgart.de (129.69.110.2)
voice: 0(049-)711-685-2053
fax:   0(049-)711-685-3706