[Info-vax] reboot due to network failure

[Phillip Helbig---undress to reply]

Recently, my switch died, which of course froze my LAN cluster.  When I 
replaced it with another one (actually a hub; I plan to buy a switch 
this week), I saw that 2 of the 3 nodes in the cluster rebooted.  What 
determines whether any nodes reboot and if so which ones?

As expected, on the non-system disks I didn't see any merges since I had
set up HBMM.  (I have swap/page disks with 2 members but on the same
node so usually these get merges in situations like this.)  The one disk
which had members mounted only on both of the nodes which rebooted got a
full shadow copy, otherwise the node that stayed up allowed minicopies
to take place. 

Interestingly, the error I mentioned here a while back about slowly 
increasing errors on a system-disk shadowset and on PEA0 has now 
disappeared; that node was one of the ones which rebooted.