The ER window showed lots of error messages about not being able to write events to the data file.
Stopped both DAQs and started new runs.
Data file e05102_2354.dat.0 is on /adaql2/data4/, which is 100% full.
Data disk /adaql2/data3 is also 100% full. Note that the last written file on data3 was for run 2347, which is the run which stopped during the owl shift.
Since I'm looking at the disk usages, I'll add the current status for both DAQ machines:
adaql1:
/dev/md10 141122104 53437324 87684780 38% /adaql1/data1 /dev/md11 141122104 70289312 70832792 50% /adaql1/data2 /dev/md12 141122104 79937536 61184568 57% /adaql1/data3 /dev/md13 141121912 52091708 89030204 37% /adaql1/data4
adaql2:
/dev/md10 141122104 53271864 80681644 40% /adaql2/data1 /dev/md11 141122104 51493232 82460276 39% /adaql2/data2 /dev/md12 141122104 133954040 0 100% /adaql2/data3 /dev/md13 141121912 133953620 0 100% /adaql2/data4