Dan, Jim, Dave:
we tried several things today to try to make h1fw0 more stable. These are:
reintroduction of h1ldasgw2 to take NDS traffic away from h1ldasgw0 (leaving it only used by h1fw0)
upgrade the network link between h1fw0 and h1ldasgw0 from a cat5e 1GE to a fiber opitcs 10GE using borrowed intel 10GE cards from LDAS
reconfigure fw0 to not write commissioning frames
power cycle fw0 and ldasgw0
these changes have not made fw0 any more stable. fw1 continues to be more stable, some of its restarts were coincident with fw0 restarts (within several minutes)
in a final attempt to make h1fw0 stable for tonight I have reduced its configuration to only save science frames (is not writing commissioning, second trends or minute trend frame files). Since that time fw0 has been stable (2 hours) with fw1 restarting once. The issue certainly appears to be file system access, we will continue our investigation tomorrow.
Note that on the DAQ overview MEDM screen, only the science frame size should match, CRC and Commissioning size numbers will not match.